From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Rik van Riel <riel@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Releases
Date: Mon, 26 Nov 2001 17:55:49 -0200 [thread overview]
Message-ID: <01112617554900.01035@manta> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111261301390.1491-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0111261301390.1491-100000@duckman.distro.conectiva>
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'.
This will eliminate 'people waiting for final 2.5.N' problem.
(2.5 is unstable, so it's normal for it to break even in silly ways
as code gets patched/rewritten)
We can't do that for 2.4, for 2.4 scenario is:
Joe User: I see this oops in 2.4.18!
Maintainer: please try this 2.4.19pre1 I made for you
J: still oopses
M: hmm... try this 2.4.19pre2
J: YES YES YES it works now thanks
- several days have passed, M may have some afterthoughts -
- and updated preN's, can feed them to J etc... -
M: Do you see anything unusual since pre2?
J: No
M: He he me is cool, let's announce 2.4.19
--
vda
next prev parent reply other threads:[~2001-11-26 15:57 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 [this message]
2001-11-26 20:42 ` Bill Davidsen
2001-11-27 4:21 ` Mike Fedyk
2001-11-27 9:50 ` Helge Hafting
-- 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=01112617554900.01035@manta \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox