From: Larry McVoy <lm@bitmover.com>
To: Paul Larson <plars@austin.ibm.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Rik van Riel <riel@conectiva.com.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Announce: daily 2.5 BK snapshots
Date: Fri, 9 Aug 2002 07:55:39 -0700 [thread overview]
Message-ID: <20020809075539.A21935@work.bitmover.com> (raw)
In-Reply-To: <1028903778.19435.348.camel@plars.austin.ibm.com>; from plars@austin.ibm.com on Fri, Aug 09, 2002 at 09:36:17AM -0500
On Fri, Aug 09, 2002 at 09:36:17AM -0500, Paul Larson wrote:
> previous day, I have a limited set of Changesets as culprits so it's
> easier for me to find the cause of problems when I do more frequent
> testing like this.
By the way, if you look at Documentation/BUG-HUNTING which describes how
to do binary search to track down bugs, you'll notice you can now do the
same thing with BK at a much finer granularity. It's possible to track
down bugs to the changeset which caused the bug, rather than the release.
Which is what Paul is talking about, but he's talking about doing it over
a small set of csets. You can do it over a large set of csets as well.
File this away as a thing you can do and if you ever need the details,
contact me and I'll walk you through it if it isn't obvious.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-08-09 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 19:52 Announce: daily 2.5 BK snapshots Jeff Garzik
2002-08-08 19:55 ` Jeff Garzik
2002-08-08 20:04 ` Rik van Riel
2002-08-08 20:17 ` Jeff Garzik
2002-08-09 14:36 ` Paul Larson
2002-08-09 14:55 ` Larry McVoy [this message]
2002-08-09 15:19 ` Martin J. Bligh
2002-08-09 15:49 ` Larry McVoy
2002-08-09 19:03 ` Paul Larson
[not found] ` <200208082127.OAA08172@cesium.transmeta.com>
2002-08-08 21:34 ` Jeff Garzik
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=20020809075539.A21935@work.bitmover.com \
--to=lm@bitmover.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@austin.ibm.com \
--cc=riel@conectiva.com.br \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox