On Tue, Mar 13, 2007 at 11:31:53PM -0400, Gene Heskett wrote: >> Now, can someone suggest a patch I can revert that might fix this? The >> total number of patches between 2.6.20 and 2.6.21-rc1 will have me >> building kernels to bisect this till the middle of June at this rate.
On Tue, Mar 13, 2007 at 10:07:21PM -0700, William Lee Irwin III wrote: > 4 billion patches could be bisected in 34 boots. Between 2.6.20 and > 2.6.21-rc1 there are only: > $ git rev-list --no-merges v2.6.20..v2.6.21-rc1 |wc -l > 3118 > patches, requiring 14 boots. In general ceil(log(n)/log(2))+2 boots. > Of course, this is a little optimistic because it assumes no additional > breakage occurring at the various bisection points. In any event, > assuming (pessimistically) 10 minutes per build, this is 280 minutes or > 4 hours and 40 minutes of build time. I estimate the process should > complete well before Friday of this week, never mind June. 33 boots for 4 billion, 13 boots for 3118, ceil(log(n)/log(2))+1 boots in general, 10 minutes/build gives 130 minutes or 2 hours, 10 minutes for 13 boots. I have no plausible explanation for these errors, and don't care to be told of any, either. -- wli - 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/
