[NFBCS] Questions about git?

[Chris Nestrud]

Brian,

You may have made changes that you haven't committed. You can commit
them to your local copy of the tree, then "git pull" any new changes.
Your changes won't be made available to others until you "git push"
them.

There is an online "Pro Git" book which is still relevant.
https://git-scm.com/book/en/v2

Chris

On Sat, Feb 22, 2025 at 09:40:53PM -0800, Brian Buhrow via NFBCS wrote:
> 	Hello everyone!  While I'm familiar with distributed source control systems like cvs and
> svn, I'm less familiar with git.  I know how to git clone a source tree to make a copy from a
> foreign source repository, but I'm less familiar with how to keep that copy current with the
> foreign repository over time.  
> 
> In my quick read of the manual, it looks like something like: git pull
> should update all my local files relative to the remote repository.  Sort of the equivalent of
> cvs update to an already checked out tree.  However,  on the particular repository I'm working
> on, git pull doesn't do what I expect and the manual is not clear to me at the moment about
> what I need to do.
> Obviously, I could erase my local tree and git clone it again, but I expect to collaborate with
> folks on this tree and that seems like a very wrong way to do it.
> 
> 	Another note I saw suggested that perhaps I need to supply the URL to the remote
> repository on the git pull command line.  Okay if that's true, but doesn't git remember the URL
> from which a local tree wa cloned?  Surely I shouldn't have to supply the URL for each git
> command if the operation I'm performing is on the same URL as the last one?
> 
> Any help with this would be greatly appreciated.
> 
> -thanks
> -Brian
> 
> 
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/ccn%40chrisnestrud.com