Re: Why can't I use git-bisect to find the first *good* commit?
>> What is the point is finding manually a commit *on the same branch* when
>> the tool can do that for you?
> Seems to me that this is trying to cram two questions into one:
>
> A) where did branch foo diverge from branch bar and
> B) which commit between that ancestor and bar did things break.
To find the answer to A, I generally just do this (using an alias):
git log --graph --oneline --all
It takes at most a couple of seconds... hardly what I'd call a manual process.
Andrew Garber <andrew@andrewgarber.com>