That's wierdly worded. So, a fetch updates your local repo with that of a remote repo, but NOT your local working copy? And a pull does the merge as well, which is remote -> local > working copy?
Terminology is rather important here. I've also see the term staging area, which I assume is the local repo. Does git have a term for what SVN calls a working copy? -Chris On Thu, Mar 1, 2012 at 2:51 PM, Barrie Treloar <[email protected]> wrote: > On Thu, Mar 1, 2012 at 1:28 PM, Chris Graham <[email protected]> wrote: > > One git specific question though, does a git pull, pull the changes all > the > > way down to your working copy? Again, sorry for the git ignorance. > > > http://stackoverflow.com/questions/292357/whats-the-difference-between-git-pull-and-git-fetch > > Quoting: > > In the simplest terms, "git pull" does a "git fetch" followed by a "git > merge". > > You can do a "git fetch" at any time to update your local copy of a > remote branch. This operation never changes any of your own branches > and is safe to do without changing your working copy. I have even > heard of people running "git fetch" periodically in a cron job in the > background (although I wouldn't recommend doing this). > > A "git pull" is what you would do to bring your repository up to date > with a remote repository. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
