From: Paul Larson <plars@austin.ibm.com>
To: "Martin J. Bligh" <Martin.Bligh@us.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: 09 Aug 2002 14:03:00 -0500 [thread overview]
Message-ID: <1028919780.22405.353.camel@plars.austin.ibm.com> (raw)
In-Reply-To: <1505209847.1028881191@[10.10.2.3]>
On Fri, 2002-08-09 at 10:19, Martin J. Bligh wrote:
> Personally, I'd love to see the *changes* in what passed and failed
> posted every day - the whole result set is obviously too big. The
> quicker people know what's wrong, the quicker it gets fixed, before
> we build more on top of an unstable foundation.
Right, that's the plan. If something changes from one day to the next,
then it will be submitted immediatly. Right now I'm in that stage of
building a "stable" foundation. It could probably use some tweaking to
the .config and other things to introduce a higher likelyhood of finding
problems from one day to the next, but I don't want to be constantly
just finding things that everyone is already aware of. Any suggestions
wrt this are welcome.
-Paul Larson
next prev parent reply other threads:[~2002-08-09 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 19:52 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
2002-08-09 15:19 ` Martin J. Bligh
2002-08-09 15:49 ` Larry McVoy
2002-08-09 19:03 ` Paul Larson [this message]
[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=1028919780.22405.353.camel@plars.austin.ibm.com \
--to=plars@austin.ibm.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®