From: Stefan Smietanowski <stesmi@stesmi.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Some thoughts about stable kernel development
Date: Sun, 09 Nov 2003 20:06:14 +0100 [thread overview]
Message-ID: <3FAE9026.60500@stesmi.com> (raw)
In-Reply-To: <m3u15de669.fsf@defiant.pm.waw.pl>
Hi Krysztof.
> As all of you know, the development cycle can be shortened by using
> two separate trees for a stable kernel line.
>
> Say, we're now at 2.4.23-rc1 stage. This "rc" kernel would also be
> known as 2.4.24-pre1. The maintainer would apply "rc"-class fixes to
> both kernels, and other patches (which can't go to "rc" kernel) would
> be applied to 2.4.24-pre1 only.
>
> After 2.4.23-rcX becomes final 2.4.23, the 2.4.24-preX would become
> 2.4.24-rc1 and would be a base for 2.4.25-pre1.
And then someone comes along and says that feature X isn't working in
some version. He then reports that "it worked in a.b.c but then someone
broke it for a.b.c+1 pre 1. Then you have to tell that person that
a.b.c+1 pre 1 isn't newer than a.b.c. Messy. Very messy.
The list gets too many mails that are answered by "RTFM" already.
// Stefan
next prev parent reply other threads:[~2003-11-09 19:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 18:41 Some thoughts about stable kernel development Krzysztof Halasa
2003-11-09 19:05 ` Valdis.Kletnieks
2003-11-12 15:05 ` Krzysztof Halasa
2003-11-09 19:06 ` Stefan Smietanowski [this message]
2003-11-12 15:07 ` Krzysztof Halasa
2003-11-12 16:04 ` Stefan Smietanowski
2003-11-12 16:51 ` Krzysztof Halasa
2003-11-13 7:33 ` Stefan Smietanowski
2003-11-13 19:55 ` Krzysztof Halasa
2003-11-09 19:26 ` Andrew Morton
2003-11-09 20:34 ` Alan Cox
2003-11-09 20:41 ` Maciej Zenczykowski
2003-11-09 19:29 ` Willy Tarreau
2003-11-12 15:01 ` Krzysztof Halasa
2003-11-09 19:50 ` John Bradford
2003-11-09 23:49 ` Valdis.Kletnieks
2003-11-10 8:53 ` John Bradford
2003-11-09 23:54 ` Rob Landley
2003-11-10 8:50 ` John Bradford
2003-11-11 7:47 ` Ryan Anderson
2003-11-11 8:19 ` Valdis.Kletnieks
2003-11-11 8:53 ` John Bradford
2003-11-10 10:58 ` Marcelo Tosatti
2003-11-12 14:48 ` Krzysztof Halasa
2003-11-10 13:35 ` jlnance
2003-11-12 14:43 ` Krzysztof Halasa
2003-11-10 16:54 ` Adrian Bunk
2003-11-12 14:40 ` Krzysztof Halasa
-- strict thread matches above, loose matches on Subject: below --
2003-11-09 21:53 Matt
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=3FAE9026.60500@stesmi.com \
--to=stesmi@stesmi.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.