From: John Alvord <jalvo@mbay.net>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel changes
Date: Thu, 04 Oct 2001 02:43:38 -0700 [thread overview]
Message-ID: <1gbort0cb2j19cm0mo9rlr21pk7f8gelml@4ax.com> (raw)
In-Reply-To: <07f901c148b8$720a6230$1a01a8c0@allyourbase> <200110040036.f940a1I08480@deathstar.prodigy.com>
In-Reply-To: <200110040036.f940a1I08480@deathstar.prodigy.com>
On Wed, 3 Oct 2001 20:36:01 -0400, davidsen@tmr.com (bill davidsen)
wrote:
>In article <07f901c148b8$720a6230$1a01a8c0@allyourbase> dmaas@dcine.com wrote:
>| > The answer is to treat all linus/ac/aa/... kernels as development
>| > kernels. Don't treat anything as stable until it's been through
>| > a real QA cycle.
>|
>| I definitely have to second what you guys are saying here... 2.2.x is the
>| stable kernel series, 2.4.x is for caffeine-fueled developers who read the
>| LKML at least once every day...
>
> Not really. I have found that 2.4 kernels are usefully stable if you
>pick them carefully.
If you run kernels from the developers, you have joined the linux
development test team... whether you know it or not. The bug reports
coming in are the main output of the test team. Positive reports are
nice but contain relatively little information for developers. You may
get productive use, and that is nice, but it is not the primary
purpose of the test team.
john alvord
next prev parent reply other threads:[~2001-10-04 9:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.b97kd6v.8j2vhi@ifi.uio.no>
[not found] ` <fa.hmvo4bv.l2gsaj@ifi.uio.no>
2001-09-29 7:29 ` Dan Maas
2001-10-04 0:36 ` bill davidsen
2001-10-04 9:43 ` John Alvord [this message]
2001-09-28 21:32 Pavel Zaitsev
2001-09-28 22:04 ` Mark Frazer
2001-09-28 22:31 ` Ben Greear
2001-09-28 22:33 ` Alan Cox
2001-10-01 9:07 ` Paul Larson
2001-09-28 22:06 ` Alan Cox
2001-09-29 13:43 ` Andrew Ebling
2001-09-29 7:25 ` Mika Liljeberg
2001-09-29 10:19 ` Ville Herva
2001-09-29 16:45 ` John Alvord
2001-09-29 17:23 ` arjan
2001-09-30 8:17 ` John Alvord
2001-10-01 17:07 ` Martin J. Bligh
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=1gbort0cb2j19cm0mo9rlr21pk7f8gelml@4ax.com \
--to=jalvo@mbay.net \
--cc=linux-kernel@vger.kernel.org \
/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®