other (none distributed) systems are certainly easier to learn. We were
fine with GIT for a few weeks, then suddenly our project is no longer
working as expected. Hope we can sort it out with a bit of professional
On Fri, Oct 5, 2012 at 2:45 AM, Konstantin Khomoutov <
> On Thu, 4 Oct 2012 03:27:02 -0700 (PDT)
> Thomas Ferris Nicolaisen <tfn...@gmail.com> wrote:
> > If you create a branch "search-label-issue" out from master, it is
> > not necessarily given that the new commits are supposed to be merged
> > back into master. It could be a throw-away experimental branch, a
> > release branch, or whatever. In any case, there would be situations
> > where it would be confusing to output the same "You are behind.."
> > thing as for tracking branches.
> Moreover, what if I merged some other branch into my
> "search-label-issue" branch and then recorded another commit -- should
> I now be made aware by Git that I'm ahead of two branches -- the one
> I initially forked off and the one I merged in and then diverged from?
> The way of thinking when working with a DVCS system requires certain
> getting into ;-)
> > What you can do instead if you want to compare what's going on
> > between your branches, is to use git logtree like I described above,
> > or more fine-grained commands like:
> > git diff master...search-label-issue
> More info on this (with pictures) can be read in
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To post to this group, send email to email@example.com.
> To unsubscribe from this group, send email to
> For more options, visit this group at
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at