From: William Lee Irwin III <wli@holomorphy.com>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New thread RDSL, post-2.6.20 kernels and amanda (tar) miss-fires
Date: Tue, 13 Mar 2007 22:07:21 -0700 [thread overview]
Message-ID: <20070314050721.GP2986@holomorphy.com> (raw)
In-Reply-To: <200703132331.56140.gene.heskett@gmail.com>
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.
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.
-- wli
next prev parent reply other threads:[~2007-03-14 5:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 8:28 New thread RDSL, post-2.6.20 kernels and amanda (tar) miss-fires Gene Heskett
2007-03-13 18:36 ` Gene Heskett
2007-03-14 3:31 ` Gene Heskett
2007-03-14 5:07 ` William Lee Irwin III [this message]
2007-03-14 5:44 ` William Lee Irwin III
2007-03-14 6:09 ` Gene Heskett
2007-03-14 6:19 ` William Lee Irwin III
2007-03-14 14:54 ` Gene Heskett
2007-03-14 21:49 ` Ray Lee
2007-03-15 3:12 ` Gene Heskett
2007-03-15 4:45 ` Ray Lee
2007-03-15 6:30 ` Gene Heskett
2007-03-15 5:28 ` [OT] " Willy Tarreau
2007-03-15 6:33 ` Gene Heskett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070314050721.GP2986@holomorphy.com \
--to=wli@holomorphy.com \
--cc=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.