From: Chris Wright <chrisw@osdl.org>
To: Nick Craig-Wood <nick@craig-wood.com>
Cc: linux-kernel@vger.kernel.org, Frank Sorenson <frank@tuxrocks.com>
Subject: Re: Stable 2.6.x.y kernel series...
Date: Tue, 7 Jun 2005 11:50:11 -0700 [thread overview]
Message-ID: <20050607185011.GB9153@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050607165906.7CB653FF9A@irishsea.home.craig-wood.com>
* Nick Craig-Wood (nick@craig-wood.com) wrote:
> In linux.kernel, Frank Sorenson wrote:
> > Nick Craig-Wood wrote:
> > > The next hurdle for 2.6.11-stable is to make sure that everything that
> > > went into it goes into 2.6.12. Is there a procedure for that?
> >
> > Other way around. In order to be accepted into -stable, it needs to
> > already have been accepted into mainline. More information at
> > http://kerneltrap.org/node/4827/54751
>
> It doesn't actually say that on the above web page. I remember it
> being discussed, but it isn't on that page (unless I've missed it of
> course ;-)
>
> It wouldn't always be appropriate either - a -stable patch might
> disable something which has a huge security hole in, wheras that sort
> of patch wouldn't get accepted in mainline.
There's lot of grey areas, those are guidelines for acceptance. And,
per your earlier comment, we do push patches to Linus where appropriate.
Typically, we prefer to see them upstream, helps add much credibility
to the stability of the patch.
next prev parent reply other threads:[~2005-06-07 18:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4cHDt-8gT-7@gated-at.bofh.it>
[not found] ` <4cHDt-8gT-9@gated-at.bofh.it>
[not found] ` <4cHDt-8gT-5@gated-at.bofh.it>
[not found] ` <4cOly-5Va-35@gated-at.bofh.it>
2005-06-07 16:59 ` Nick Craig-Wood
2005-06-07 18:50 ` Chris Wright [this message]
2005-06-07 19:30 ` Nick Craig-Wood
[not found] <4bt9p-2OQ-3@gated-at.bofh.it>
[not found] ` <4cud6-5gm-17@gated-at.bofh.it>
2005-06-07 8:26 ` Nick Craig-Wood
2005-06-07 15:16 ` Frank Sorenson
2005-06-07 17:54 ` Bill Davidsen
2005-06-03 22:43 Jeff Garzik
2005-06-03 23:10 ` Grant Coady
2005-06-06 13:25 ` szonyi calin
2005-06-06 13:33 ` Arjan van de Ven
2005-06-06 17:58 ` Alan Cox
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=20050607185011.GB9153@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=frank@tuxrocks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@craig-wood.com \
/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®