From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Paul Larson <plars@linuxtestproject.org>
Cc: Edesio Costa e Silva <edesio@ieee.org>,
lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>,
Edesio Costa e Silva <edesio@task.com.br>
Subject: Re: 2.5.60 cheerleading...
Date: Thu, 13 Feb 2003 16:54:32 +0100 [thread overview]
Message-ID: <20030213155432.GA30401@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1045150153.28493.10.camel@plars>
On Thu, 13 February 2003 09:29:12 -0600, Paul Larson wrote:
>
> If Linus really is building and booting every kernel prior to release,
> it would be quick and simple to add a fast subset of LTP to the mix and
> do a quick regression run. It's convenient, fast and could save a lot
> of headaches for a lot of people later on.
The problem I see with this approach is that "a lot of people" scales
far better than Linus.
Saving 100 people a day of work by offloading it to Linus is quite an
optimisation, but it doesn't optimize the overall development speed.
Let the crowd build the kernel, see the breakage and fix it up, until
we get back to -preX and -rcY kernels.
Jörn
--
Victory in war is not repetitious.
-- Sun Tzu
next prev parent reply other threads:[~2003-02-13 15:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 15:52 Jeff Garzik
2003-02-12 16:00 ` Paul Larson
2003-02-12 16:09 ` Jeff Garzik
2003-02-12 18:07 ` Dave Jones
2003-02-12 18:44 ` John Bradford
2003-02-12 18:17 ` Scott Robert Ladd
2003-02-12 18:41 ` John Bradford
2003-02-12 18:55 ` Dave Jones
2003-02-12 18:43 ` Paul Larson
2003-02-12 19:33 ` Edesio Costa e Silva
2003-02-13 15:29 ` Paul Larson
2003-02-13 15:54 ` Jörn Engel [this message]
2003-02-13 16:03 ` Dave Jones
2003-02-13 16:55 ` Paul Larson
2003-02-13 17:11 ` John Bradford
2003-02-13 18:04 ` Paul Larson
2003-02-13 18:23 ` John Bradford
2003-02-13 21:16 ` Paul Larson
2003-02-13 21:38 ` Jeff Garzik
2003-02-13 21:54 ` John Bradford
2003-02-13 21:57 ` Paul Larson
2003-02-13 22:11 ` John Bradford
2003-02-13 22:20 ` Valdis.Kletnieks
2003-02-13 22:39 ` Paul Larson
2003-02-13 22:43 ` Randy.Dunlap
2003-02-13 22:53 ` Paul Larson
2003-02-13 22:58 ` John Bradford
2003-02-14 6:36 ` Paul Larson
2003-02-20 22:29 ` Timothy D. Witham
2003-02-20 22:42 ` Jeff Garzik
2003-02-20 22:46 ` Timothy D. Witham
2003-02-14 1:21 ` Martin J. Bligh
2003-02-14 1:32 ` Linus Torvalds
2003-02-14 3:24 ` Mike Dresser
2003-02-14 9:08 ` John Bradford
2003-02-14 4:10 ` Werner Almesberger
2003-02-13 17:06 ` 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=20030213155432.GA30401@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=edesio@ieee.org \
--cc=edesio@task.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@linuxtestproject.org \
--cc=torvalds@transmeta.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 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®