From: Daniel Andersen <anddan@linux-user.net>
To: "Sartorelli, Kevin" <Kevin.Sartorelli@openpolytechnic.ac.nz>
Cc: fraga@abusar.org, linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: Linux 2.6.9-rc1
Date: Wed, 25 Aug 2004 03:05:16 +0200 [thread overview]
Message-ID: <412BE5CC.8020303@linux-user.net> (raw)
In-Reply-To: <4B2093FFC31B7A45862B62A376EA7176033C058D@mickey.topnz.ac.nz>
Sartorelli, Kevin wrote:
> Daniel Andersen wrote:
>
>>As Linus initially said, there is the possibility of releasing
>>a bug-fix patch 2.6.8.2 *after* 2.6.9 has been released.
>
>
> So, in this case, which would be considered the latest stable kernel to be used in production? I can see this getting to a stage where you just pick and hope :-(
>
> Cheers
> Kevin
This would normally be 2.6.9(.w). I did not point it out but Linus said
-rc kernels.
Lately there has been some talk about removing deprecated features (eg.
devfs, cryptoloop) which makes me think. 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.
In this case Kevin would have a point.
Daniel Andersen
--
next prev parent reply other threads:[~2004-08-25 1:04 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 0:31 Linux 2.6.9-rc1 Sartorelli, Kevin
2004-08-25 1:05 ` Daniel Andersen [this message]
2004-08-25 1:20 ` Linus Torvalds
2004-08-25 14:52 ` Martin J. Bligh
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 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-25 23:44 ` David S. Miller
2004-08-26 3:14 ` Joshua Kwan
2004-08-26 8:02 ` Harald Welte
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=412BE5CC.8020303@linux-user.net \
--to=anddan@linux-user.net \
--cc=Kevin.Sartorelli@openpolytechnic.ac.nz \
--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 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.