Re: git-bisect not working correctly in the kvm.git repository?

[Linus Torvalds <torvalds@linux-foundation.org>]

On Mon, 17 Nov 2008, walt wrote:
> 
> Okay, that's clearly what's happening to me.  The kvm.git repo
> contains hundred of commits just like that.  How would you deal
> with the same situation?  Is git-bisect skip the easiest way?

Yeah. A much fancier alternative is to do a (temporary) branch that 
rewrites the history using the same sub-tree merge strategy, so that you 
can actually build the whole thing in that branch. 

This, btw, is why I asked Chris Mason to not do a subtree merge for the 
btrfs code. I wrote him a helper script to do exactly that with a nice 
index script for 'git filter-branch'. That way his whole tree is nicely 
bisectable when merged into the rest of the kernel.

But that's really a rather bigger thing to do, and I'd suggest that only 
if you really can't find things any other way.

		Linus