From: Andi Kleen <ak@muc.de>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Arjan van de Ven <arjan@infradead.org>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, Chris Wright <chrisw@osdl.org>,
torvalds@osdl.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] -stable, how it's going to work.
Date: Fri, 11 Mar 2005 08:07:52 +0100 [thread overview]
Message-ID: <m1ekemzmlz.fsf@muc.de> (raw)
In-Reply-To: <4231258C.3060400@nortel.com> (Chris Friesen's message of "Thu, 10 Mar 2005 22:58:52 -0600")
Chris Friesen <cfriesen@nortel.com> writes:
> Neil Brown wrote:
>
>> If a data corruption bug has been there for 10 weeks without being
>> noticed, then the real risk is not that great. We are calling it
>> "-release", not "-hardened".
>
> I disagree. If there's a simple, obvious, small fix that passes all
> the other criteria, it should go into -stable ASAP after passing
> review. Then the -stable maintainers will push the fix to
> Andrew/Linux, and it will go into the next 2.6.x.
No way, it needs to go into mainline first and then maybe later
into stable. Doing stable first would lead to code drift because
a lot of people would only care about stable and we would be back
in the bad old days when older kernels had more fixes than newer
ones.
-Andi
next prev parent reply other threads:[~2005-03-11 7:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 7:28 [RFC] -stable, how it's going to work Greg KH
2005-03-09 9:56 ` Andi Kleen
2005-03-09 10:10 ` Arjan van de Ven
2005-03-09 10:17 ` Russell King
2005-03-09 10:24 ` Arjan van de Ven
2005-03-09 10:32 ` Russell King
2005-03-09 10:28 ` Andi Kleen
2005-03-09 14:20 ` Marcelo Tosatti
2005-03-09 18:00 ` Alan Cox
2005-03-09 18:29 ` Greg KH
2005-03-09 18:29 ` Chris Wright
2005-03-09 19:30 ` Andi Kleen
2005-03-09 18:28 ` Chris Wright
2005-03-09 19:44 ` Andi Kleen
2005-03-09 20:16 ` Chris Wright
2005-03-09 22:49 ` Russell King
2005-03-09 18:34 ` Greg KH
2005-03-09 19:39 ` Andi Kleen
2005-03-09 20:03 ` Greg KH
2005-03-09 20:25 ` Bill Davidsen
2005-03-10 10:00 ` Neil Brown
2005-03-10 10:17 ` Arjan van de Ven
2005-03-11 1:49 ` Neil Brown
2005-03-11 4:58 ` Chris Friesen
2005-03-11 7:07 ` Andi Kleen [this message]
2005-03-10 16:43 ` Greg KH
2005-03-10 17:27 ` Lee Revell
2005-03-10 17:31 ` Greg KH
2005-03-10 18:25 ` Lee Revell
2005-03-11 10:13 ` Pavel Machek
2005-03-10 17:43 ` Chris Wright
2005-03-10 17:51 ` Lee Revell
2005-03-10 17:44 ` Linus Torvalds
2005-03-11 0:10 ` Neil Brown
2005-03-11 2:43 ` J. Bruce Fields
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=m1ekemzmlz.fsf@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=cfriesen@nortel.com \
--cc=chrisw@osdl.org \
--cc=greg@kroah.com \
--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