From: Bill Davidsen <davidsen@tmr.com>
To: Frank Sorenson <frank@tuxrocks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stable 2.6.x.y kernel series...
Date: Tue, 07 Jun 2005 13:54:48 -0400 [thread overview]
Message-ID: <42A5DF68.6040700@tmr.com> (raw)
In-Reply-To: <42A5BA66.8040504@tuxrocks.com>
Frank Sorenson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Nick Craig-Wood wrote:
>
>>Hearty agreement from me.
>>
>>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's more complex than that, because -stable allows simple fixes while a
complex fix or even total rethink may be in mainline. I'm personally
happy with that, although I don't know if it has actually happened.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-06-07 17:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4bt9p-2OQ-3@gated-at.bofh.it>
[not found] ` <4cud6-5gm-17@gated-at.bofh.it>
2005-06-07 8:26 ` Stable 2.6.x.y kernel series Nick Craig-Wood
2005-06-07 15:16 ` Frank Sorenson
2005-06-07 17:54 ` Bill Davidsen [this message]
[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
2005-06-07 19:30 ` Nick Craig-Wood
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=42A5DF68.6040700@tmr.com \
--to=davidsen@tmr.com \
--cc=frank@tuxrocks.com \
--cc=linux-kernel@vger.kernel.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