From: Paul Larson <plars@austin.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Frazer <mark@somanetworks.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel changes
Date: 01 Oct 2001 09:07:07 +0000 [thread overview]
Message-ID: <1001927233.8597.6.camel@plars.austin.ibm.com> (raw)
In-Reply-To: <E15n6CR-00008r-00@the-village.bc.nu>
In-Reply-To: <E15n6CR-00008r-00@the-village.bc.nu>
On 28 Sep 2001 23:33:39 +0100, Alan Cox 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've heard Suse, RedHat and the like don't do a
> > bad job at this.
>
> We try. If you want to QA your own kernel the cerberus test suite is
> publically available - and indeed the VA guys are to thank for its origins.
>
> Alan
For Linux QA/Testing, you may also want to check out the Linux Test
Project. We just had a new release that added about 400 new testcases
which is way up from what we had before. We also have descriptions for
all the tests now too.
-Paul Larson
next prev parent reply other threads:[~2001-10-01 14:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[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
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=1001927233.8597.6.camel@plars.austin.ibm.com \
--to=plars@austin.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@somanetworks.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®