From: Andi Kleen <ak@muc.de>
To: Arjan van de Ven <arjan@infradead.org>, Greg KH <greg@kroah.com>,
Chris Wright <chrisw@osdl.org>,
torvalds@osdl.org, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] -stable, how it's going to work.
Date: 9 Mar 2005 11:28:30 +0100
Date: Wed, 9 Mar 2005 11:28:30 +0100 [thread overview]
Message-ID: <20050309102830.GA76065@muc.de> (raw)
In-Reply-To: <20050309101728.A17289@flint.arm.linux.org.uk>
On Wed, Mar 09, 2005 at 10:17:28AM +0000, Russell King wrote:
> On Wed, Mar 09, 2005 at 11:10:59AM +0100, Arjan van de Ven wrote:
> > On Wed, 2005-03-09 at 10:56 +0100, Andi Kleen wrote:
> > > One rule I'm missing:
> > >
> > > - It must be accepted to mainline.
> > >
> >
> > I absolutely agree with Andi on this one.
>
> What about the case (as highlighted in previous discussions) that the
> stable tree needs a simple "dirty" fix, whereas mainline takes the
> complex "clean" fix?
That's ok, as long as the maintainers agree it's an equivalent fix
What should just be ruled out is something getting fixed in stable
and not getting fixed in mainline. And the mainline patch should
always go in first and preferably tested for a short time there.
But in general it is a judgement call: if the "big fix" is not too big
or risky I would prefer the big fix just to avoid code drift.
A custom fix for stable should be more the exception than the rule.
-Andi
next prev parent reply other threads:[~2005-03-09 10:29 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 [this message]
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
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=20050309102830.GA76065@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--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