On Mon, Sep 05, 2005 at 01:45:28AM -0700, Linus Torvalds wrote: > > On Mon, 5 Sep 2005, Rolf Eike Beer wrote: > > > > The problem appeared between 2.6.12-git3 and 2.6.12-git4. > > Just for reference, that's git ID's > > > 1d345dac1f30af1cd9f3a1faa12f9f18f17f236e..2a5a68b840cbab31baab2d9b2e1e6de3b289ae1e > > and that's 225 commits and the diff is 55,781 lines long. > > It would be very good if you could try to use raw git and narrow it down a > bit more. It's really easy these days with a recent git version, just do > > git bisect start > git bisect good 1d345dac1f30af1cd9f3a1faa12f9f18f17f236e > git bisect bad 2a5a68b840cbab31baab2d9b2e1e6de3b289ae1e > > and off you go.. That will select a new kernel for you to try, which > basically cuts down the commits to ~110 - and if you can test just a few > kernels and binary-search a bit more, we'd have it down to just a couple.
Can this method detect breakages that are spread across more than one patch? I suppose it'll just trigger on the last patch commited in the set in this case? Sonny - 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/
