Re: git-bisect problem

Andrew Morton [off-list ref] writes:

quoted

As humans, we can tell that it is not very plausible that the
 EXTRAVERSION change caused whatever breakage you are chasing,
 but sorry, from your log, I think bisect is doing the right
 thing.

I don't think humans are well-suited to using git.

I did not mean that ;-).  Git is not as smart as humans.

My current theory is that I was bisecting Linus's tree all along.

Sorry, I did not realize that was _not_ what you were doing.
Your log started by saying 2.6.16-rc1 is good but 2.6.16-rc2 was
not, so I just assumed your bug was between those two.

If your suspect was merged between these two versions, then it
does not matter which branch you were _on_ when you started to
bisect.  

You mark points that are good and bad, and wander around in the
commit DAG, trying to narrow down the distance between known
good points and bad points while bisecting, and during that, you
are not really on _any_ branch.