Error message with 'bisect'

Mathieu Poirier mathieu.poirier at canonical.com
Fri Jul 9 20:33:26 UTC 2010


Andy,

I started investigating the "bisect" command as you suggested on Friday.
After having a few successful runs with the tool, I isolated my problem
to a check in between rc3 and rc4... But there is 425 of them.  

So what better tool than "bisect" to sort through all this !  I checkout
a fresh upstream tree and set out to bisect but got an error message:

mpoirier at black:~/canonical/linus$ git bisect start
mpoirier at black:~/canonical/linus$ git bisect good v2.6.35-rc4
mpoirier at black:~/canonical/linus$ git bisect bad v2.6.35-rc3
Some good revs are not ancestor of the bad rev.
git bisect cannot work properly in this case.
Maybe you mistake good and bad revs?
mpoirier at black:~/canonical/linus$


Tim tried on his own tree and got the same issue.  Would you know what
is going on ?

Thanks, Mathieu.





More information about the kernel-team mailing list