From: Andy Isaacson <adi@bitmover.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Christian <evil@g-house.de>,
linux-kernel@vger.kernel.org, support@bitmover.com
Subject: Re: tarballs of patchsets?
Date: Tue, 25 May 2004 09:02:00 -0700 [thread overview]
Message-ID: <20040525160200.GA30213@bitmover.com> (raw)
In-Reply-To: <20040524105552.311a990b.akpm@osdl.org>
On Mon, May 24, 2004 at 10:55:52AM -0700, Andrew Morton wrote:
> Christian <evil@g-house.de> wrote:
> > i am trying to chase some bug and i know, it must be somewhere
> > between 2.6.4 and 2.6.5.
>
> The most practical way of doing this would be to download bitkeeper and do
> a binary search.
>
> 1: Do `bk changes > foo'.
[snip]
> 2: Do
> bl clone -ql -r1.1734 ref-repo test-repo
[snip]
> 3: cd test-repo ; bk -r get
> 4: build, test, choose new revision, goto step 1.
FWIW, we're batting around the idea of automating this -- it would be
cool (and quite trivial) to have a "bk-findbug.sh" script that takes
- a repo
- "I know the bug wasn't present in 1.1562"
- "the bug is present in 1.1699"
- a shell fragment that exits 1 if the bug exists, 0 if the bug is squashed
and tells you which cset causes the bug to appear.
But, applying this to the kernel is more problematic; you have to
reboot, or run under vmware/UML/Xen/whatever.
-andy
prev parent reply other threads:[~2004-05-25 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 16:15 tarballs of patchsets? Christian
2004-05-24 16:33 ` Christian
2004-05-24 17:55 ` Andrew Morton
2004-05-24 22:02 ` Christian
2004-05-25 16:02 ` Andy Isaacson [this message]
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=20040525160200.GA30213@bitmover.com \
--to=adi@bitmover.com \
--cc=akpm@osdl.org \
--cc=evil@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--cc=support@bitmover.com \
/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.