From: Junio C Hamano Date: Fri, 06 Mar 2009 22:21:50 GMT Subject: Re: fetch and pull Message-ID: <7v7i32s35t.fsf@gitster.siamese.dyndns.org> In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E70A115F5D@EXCHANGE.trad.tradestation.com> "John Dlugosz" writes: > Here is what I'm "cooking": > > ======excerpt====== > > To keep apprised of other people's work, including updates to the main > dev branch, start the day with: > > git fetch > > This will update your "remote tracking branches", letting you see what > everyone else is working on, and letting you see the central > repository's dev (as remotes/origin/dev) compared to your own local dev, > so you can see what has been added. > > This does not change your local dev, or any other branches you are > using. As for your own topic branches, you are the only one who changes > them. This is a perfectly safe command and can be performed any time to > update your view of what's happening throughout the team. > You will, in particular, see your local dev where you last left it, and > the current remotes/origin/dev pointing ahead of it. E.g. > > A <== dev > \ > B--C--D <== remotes/origin/dev > > In this example, you see plain "dev" still pointing to A, and > "remotes/origin/dev" pointing to D. So, you can tell that B, C, D were > added. Review the nodes B, C, and D, by reading the comments and seeing > which files were affected, and look deeper if it seems to affect what > you are doing. Finally, issue the command > > ??? > > And this will update your local dev to match the origin. > > ====== I already answered that question in a separate message (that is different from what you are replying to), didn't I?