public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Releases
Date: Tue, 27 Nov 2001 16:08:44 -0200	[thread overview]
Message-ID: <01112716084403.00872@manta> (raw)
In-Reply-To: <Pine.LNX.4.33.0111261807570.489-100000@mikeg.weiden.de>
In-Reply-To: <Pine.LNX.4.33.0111261807570.489-100000@mikeg.weiden.de>

On Monday 26 November 2001 16:45, Mike Galbraith wrote:
> On Mon, 26 Nov 2001, vda wrote:
> > On Monday 26 November 2001 13:02, Rik van Riel wrote:
> > > On Mon, 26 Nov 2001, Ian Stirling wrote:
> > > > However, I for one never run a -pre kernel.
> > > >
> > > > I don't run -pre, because rightly or wrongly, I've got the impression
> > > > that these get even less testing than releases.
> > >
> > > I think the opening sentence of your email states
> > > the reason for that pretty well.
> >
> > The only way we can get good testing for new kernels is to stop using
> > -preN prefix in development branch (2.5.x). Just increment that 'x'.
>
> That won't change anything except the number on the kernel.  The people
> who you're trying to turn into bleeding edge testers (those who stay a
> little behind [bignum]) will continue to ride the curve at the point of
> their choosing.

Yes, but they can't tell which 2.5.x is more stable just from version number.
This way Linus will get better test coverage in 2.5.x.

Those who need stability can read lkml and figure out which 2.5.x was 
'glitchless' :-) or stick with 2.4.x
--
vda

       reply	other threads:[~2001-11-27 14:11 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0111261807570.489-100000@mikeg.weiden.de>
2001-11-27 18:08 ` vda [this message]
2001-11-27 16:58   ` Kernel Releases Mike Galbraith
     [not found] <fa.dac7a7v.1hkofg8@ifi.uio.no>
2001-11-27 17:53 ` Giacomo Catenazzi
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
  -- strict thread matches above, loose matches on Subject: below --
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-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-25  4:27 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

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=01112716084403.00872@manta \
    --to=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    /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