From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Linus Torvalds <torvalds@osdl.org>,
Daniel Andersen <anddan@linux-user.net>
Cc: "Sartorelli, Kevin" <Kevin.Sartorelli@openpolytechnic.ac.nz>,
fraga@abusar.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.9-rc1
Date: Wed, 25 Aug 2004 07:52:29 -0700 [thread overview]
Message-ID: <147680000.1093445547@[10.10.2.4]> (raw)
In-Reply-To: <Pine.LNX.4.58.0408241818030.17766@ppc970.osdl.org>
>> Linus, is there a chance that
>> there will be a x.y.z.W release of an old kernel after the next x.y.Z.w
>> has been released and no longer is -rc? For example releasing a 2.6.8.2
>> after 2.6.9 has been released and no longer is a 2.6.9-rcX.
>
> I don't see the point of such a release, so I'd say "no". Once we have a
> stable kernel, we make updates to _that_ one, not older ones.
>
> HOWEVER - there may well be exceptions to this brought on by distribution
> usage etc. For example, if some distribution ends up basing it's work on
> (say) 2.6.8.1, and we later find a bug, we might release a 2.6.8.2 even
> though we might have done a 2.6.9 or even 2.6.10 later - just as a way to
> support the existing users who take a long time to update.
>
> I consider that a pretty remote possibility, though. It's a lot more
> likely that the distribution-maker itself just does it's own patch on top
> of whatever release he started off with.
My assumption would be that once 2.6.9 is released, it's not uber-stable
immediately ... so it'd be nice to keep at least one minor rev back
going on the bugfix stream (eg 2.6.8.X) .... for people who want an
uber-stable kernel. Doing more than 1 back would indeed seem
counter-productive.
That said it's unlikely there would still be urgent fixes for 2.6.8 a few
weeks after it was released, but it seems like the right thing to do, at
least in principle (maybe for a security fix, or something).
M.
next prev parent reply other threads:[~2004-08-25 14:55 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 0:31 Sartorelli, Kevin
2004-08-25 1:05 ` Daniel Andersen
2004-08-25 1:20 ` Linus Torvalds
2004-08-25 14:52 ` Martin J. Bligh [this message]
2004-08-25 21:14 ` Roman Zippel
2004-08-26 8:09 ` Denis Vlasenko
2004-08-26 8:35 ` Geert Uytterhoeven
2004-08-27 12:45 ` Horst von Brand
2004-08-27 21:30 ` Denis Vlasenko
2004-08-25 20:27 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 22:20 David Mansfield
2004-08-24 7:49 Linus Torvalds
2004-08-24 16:41 ` Pierre Ossman
2004-08-24 16:46 ` Russell King
2004-08-24 16:59 ` Pierre Ossman
2004-08-24 17:50 ` Alexander Gran
2004-08-24 18:42 ` Matt Mackall
2004-08-24 19:23 ` Linus Torvalds
2004-08-24 19:38 ` Chris Meadors
2004-08-24 19:54 ` Florian Weimer
2004-08-24 20:13 ` Josh Boyer
2004-08-24 20:25 ` Jesper Juhl
2004-08-24 20:07 ` Tim Schmielau
2004-08-24 20:32 ` Matt Mackall
2004-08-24 21:22 ` Martin J. Bligh
2004-08-24 22:55 ` Dave Hansen
2004-08-24 22:52 ` H. Peter Anvin
2004-08-24 23:46 ` Dâniel Fraga
2004-08-25 0:11 ` Daniel Andersen
2004-08-25 1:01 ` Dâniel Fraga
2004-08-25 4:24 ` H. Peter Anvin
2004-08-25 20:36 ` Bill Davidsen
2004-08-25 0:25 ` Stephen Wille Padnos
2004-08-25 1:11 ` Dâniel Fraga
2004-08-25 9:13 ` Geert Uytterhoeven
2004-08-25 20:18 ` Bill Davidsen
2004-08-24 18:54 ` Chris Wedgwood
2004-08-24 21:48 ` H. Peter Anvin
2004-08-24 21:58 ` Randy.Dunlap
2004-08-25 14:45 ` Chris Friesen
2004-08-25 16:12 ` Matthias Andree
2004-08-25 18:52 ` Joshua Kwan
2004-08-25 20:32 ` Harald Welte
2004-08-25 21:35 ` Henrik Nordstrom
2004-08-25 23:48 ` Harald Welte
2004-08-25 23:44 ` David S. Miller
2004-08-26 3:14 ` Joshua Kwan
2004-08-26 8:02 ` Harald Welte
2004-08-26 5:07 ` Mark Lord
[not found] ` <20040825231407.058b3ea6.davem@redhat.com>
2004-08-26 6:15 ` David S. Miller
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='147680000.1093445547@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=Kevin.Sartorelli@openpolytechnic.ac.nz \
--cc=anddan@linux-user.net \
--cc=fraga@abusar.org \
--cc=linux-kernel@vger.kernel.org \
--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 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®