From: Arjan van de Ven <arjan@infradead.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Andi Kleen <ak@muc.de>, 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: Wed, 09 Mar 2005 11:24:58 +0100 [thread overview]
Message-ID: <1110363899.6280.77.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050309101728.A17289@flint.arm.linux.org.uk>
On Wed, 2005-03-09 at 10:17 +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 the exception I talked about a bit later in my mail. It should be
rare and very deliberate. And in fact once the mainline change ripples
out into maturity I rather replace the -stable one with that later on,
even if it's a bit more invasive.
next prev parent reply other threads:[~2005-03-09 10:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 7:28 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 [this message]
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
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=1110363899.6280.77.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--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®