Linus Torvalds <[EMAIL PROTECTED]> wrote: > > If you remember/save the good/bad commit ID's, you can restart the whole > process and just feed the correct state for the ID's: > > git bisect start > git bisect bad v2.6.13-rc5 > git bisect good v2.6.13-rc4 > .. here bisect will start narrowing things down .. > git bisect bad <sha1 of known bad> > git bisect good <sha1 of known good> > ..
What do you suggest should be done if you hit a compile error partway through the bisection search? Is there some way to go forward or backward a few csets while keeping the search markers sane? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/