From: Paul Larson <plars@linuxtestproject.org>
To: John Bradford <john@grabjohn.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
davej@codemonkey.org.uk, edesio@ieee.org,
lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>,
edesio@task.com.br
Subject: Re: 2.5.60 cheerleading...
Date: 13 Feb 2003 15:57:56 -0600 [thread overview]
Message-ID: <1045173477.28494.66.camel@plars> (raw)
In-Reply-To: <200302132154.h1DLs3ar012874@darkstar.example.net>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Thu, 2003-02-13 at 15:54, John Bradford wrote:
> Likewise with kernel releases - fewer, larger releases work fine and
> mean less effort for developers, unless something breaks, in which
> case there is a lot to go through to locate the problem, and people
> who can't boot the broken kernel have to wait longer to test other
> things that were newly merged in that release.
This was exactly what I was getting at. I suspect that there are a good
number of people that try to boot a 2.5 kernel for testing, run into
immediate problems, and shelve the idea of 2.5 testing for a couple of
months because of an immediate appearance that 2.5 is too unstable to
test. I've seen frequent griping that not enough testing happens, the
idea is to get it to a point where more people can test it _without_
adding a huge delay or making a huge gap between releases.
On Thu, 2003-02-13 at 15:38, Jeff Garzik wrote:
> Outside suggestions to "improve" Linus's workflow usually fall upon deaf
> ears...
Since Linus hasn't chimed in yet, I'm guessing that's exactly what
happened. I'm not trying to improve his workflow, but rather the
workflow of anyone who might be interested in getting more involved in
2.5 testing.
-Paul Larson
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-02-13 21:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 15:52 2.5.60 cheerleading 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
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 [this message]
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=1045173477.28494.66.camel@plars \
--to=plars@linuxtestproject.org \
--cc=davej@codemonkey.org.uk \
--cc=edesio@ieee.org \
--cc=edesio@task.com.br \
--cc=jgarzik@pobox.com \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.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 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.