From: Tim Gardner <rtg.canonical@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Latest kernel stable/longterm status
Date: Wed, 11 Jan 2012 11:10:14 +0100 [thread overview]
Message-ID: <4F0D6006.40506@canonical.com> (raw)
In-Reply-To: <20120110235612.GB1507@kroah.com>
On 01/11/2012 12:56 AM, Greg KH wrote:
> On Tue, Jan 10, 2012 at 11:03:33AM +0100, Tim Gardner wrote:
>> On 01/10/2012 03:26 AM, Steven Rostedt wrote:
>>> On Mon, Jan 09, 2012 at 04:37:05PM -0800, Greg KH wrote:
>>>> As 3.2 is now out, here's a note as to the current status of the
>>>> different stable/longterm kernel trees.
>>>
>>> Thanks for all your hard work Greg!
>>>
>>
>> I'd also like to thank Greg.
>>
>> Ubuntu will continue to support 2.6.32.y until April 2015. Ubuntu
>> has also chosen 3.2 as a long term supported kernel for the 12.04
>> release and will pick up support for it when 3.3 is released.
>
> What exactly do you mean by this?
>
> greg k-h
If you're agreeable, I would very much prefer to continue with the
stable update model that you've developed by committing to the
linux-2.6.32.y and linux-3.2.y branches in
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git.
The mailing list review process as well as the policies regarding patch
suitability are working well.
rtg
--
Tim Gardner tim.gardner@canonical.com
next prev parent reply other threads:[~2012-01-11 10:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 0:37 Greg KH
2012-01-10 2:26 ` Steven Rostedt
2012-01-10 10:03 ` Tim Gardner
2012-01-10 23:56 ` Greg KH
2012-01-11 1:38 ` Anca Emanuel
2012-01-11 10:10 ` Tim Gardner [this message]
2012-01-11 15:12 ` Greg KH
2012-01-11 20:37 ` Tim Gardner
2012-01-11 20:52 ` Greg KH
2012-01-21 13:36 ` Willy Tarreau
2012-01-21 13:47 ` Greg KH
2012-01-21 14:45 ` Willy Tarreau
2012-01-11 12:32 ` Geert Uytterhoeven
2012-01-11 12:42 ` Geert Uytterhoeven
2012-01-11 15:13 ` Greg KH
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=4F0D6006.40506@canonical.com \
--to=rtg.canonical@gmail.com \
--cc=ben@decadent.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tim.gardner@canonical.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
Powered by JetHome