public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@idb.hist.no>
To: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel Releases
Date: Tue, 27 Nov 2001 10:50:09 +0100	[thread overview]
Message-ID: <3C0361D1.A4EA110F@idb.hist.no> (raw)
In-Reply-To: <Pine.LNX.3.96.1011126151758.27112G-100000@gatekeeper.tmr.com>

Bill Davidsen wrote:
> 
> On Sun, 25 Nov 2001, David Relson wrote:
> 
> I wish you luck. About 18 months ago I offered to set up a testing group
> to take kernel source before it with up for ftp and to compile it on
> various x86, SPARC{32,64}, and ALPHA machines to be sure it would at least
> compile. I was told with varying degrees of rudeness that it would delay
> the releases (that is a GOOD thing in stable kernels), and that I should
> avoid the 2.4 series and use the "stable" 2.2 kernsls (2.4 IS a stable
> kernel of course, although you would never gues it).
> 

Nobody's against you running a compile-test setup.  What they don't like
is the part about not releasing it until you have tested it.
That's because many others want to test too!
This is necessary - some may test aspects other than mere compiling.
Or perhaps a compiler different from yours.

Feel free to serve "known good" kernels - the masses who don't read
changelogs
or don't want to risk possible new bugs will surely appreciate this.

Just don't limit those of us who want to test the very latest - even
kernels with known bugs.  Maybe the bug won't bother me because I
don't use that driver/fs and things like that.  I want the kernel even
if, say, minixfs is broken.

Downloading the latest kernel is _not_ for those who can't deal
with occational trouble.  
Pre or no pre - development or "stable" series.
Those who run the latest is the testing team.  If they don't want to
be, they go for kernels at least a couple of weeks old that haven't
gathered trouble reports.  

Helge Hafting

  parent reply	other threads:[~2001-11-27  9:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-25  4:27 Kernel Releases David Relson
2001-11-25  5:49 ` John Alvord
2001-11-25  6:34   ` CaT
2001-11-25 14:12   ` John Jasen
2001-11-26  7:15     ` John Alvord
2001-11-25 15:46   ` Eric W. Biederman
2001-11-25 16:23     ` Nathan Walp
2001-11-26 21:03     ` Bill Davidsen
2001-11-25 19:55 ` Phil Sorber
2001-11-26  9:22 ` Allan Sandfeld
2001-11-26 14:51   ` Ian Stirling
2001-11-26 15:02     ` Rik van Riel
2001-11-26 19:11       ` Ian Stirling
2001-11-26 19:55       ` vda
2001-11-26 20:42 ` Bill Davidsen
2001-11-27  4:21   ` Mike Fedyk
2001-11-27  9:50   ` Helge Hafting [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-25  5:37 Dan Kegel
2001-11-25  9:25 ` Nathan Dabney
2001-11-25 10:24   ` Keith Owens
2001-11-25 13:34     ` Phil Howard
2001-11-25 19:03     ` Nathan Dabney
2001-11-26 10:46 Martin Knoblauch
2001-11-26 15:27 ` John Jasen
2001-11-26 20:36   ` Horst von Brand
2001-11-27  2:40     ` Gerhard Mack
2001-11-27 17:25 Dan Kegel
2001-11-27 17:36 ` François Cami
2001-11-27 17:38   ` Dan Kegel
2001-11-27 18:13     ` Vitaly Luban
2001-11-28 16:23     ` Horst von Brand
2001-11-28 19:17       ` Mike Fedyk
     [not found] <fa.dac7a7v.1hkofg8@ifi.uio.no>
2001-11-27 17:53 ` Giacomo Catenazzi
     [not found] <Pine.LNX.4.33.0111261807570.489-100000@mikeg.weiden.de>
2001-11-27 18:08 ` vda
2001-11-27 16:58   ` Mike Galbraith

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=3C0361D1.A4EA110F@idb.hist.no \
    --to=helgehaf@idb.hist.no \
    --cc=davidsen@tmr.com \
    --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