mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Leann Ogasawara <leann.ogasawara@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Next Long Term Stable?
Date: Thu, 21 Nov 2013 09:30:02 -0800	[thread overview]
Message-ID: <20131121173002.GB21986@kroah.com> (raw)
In-Reply-To: <CAAE8-rJ3SyKCD8BXphCE5d42p1pf1EW5e7ngnuJZ17VpbnMP5Q@mail.gmail.com>

On Wed, Nov 20, 2013 at 03:42:26PM -0800, Leann Ogasawara wrote:
> Hi Greg,
> 
> I realize it's likely too early to even be inquiring about the next
> Longterm Stable kernel you'd be selecting to maintain, especially
> since you've recently selected the v3.10 kernel.  However, I thought
> it wouldn't hurt to at least mention that Ubuntu will anticipate
> shipping a v3.13 based kernel for the upcoming Ubuntu 14.04 LTS
> release happening in April 2014.  If it were possible, I know the
> Ubuntu kernel engineers would be interested in aligning and
> contributing to the next Long Term Stable Kernel you choose.  At the
> very least, I hope this information gives you at least one extra data
> point for when you do select the next Longterm Stable kernel you plan
> to maintain.  Thanks again for all the stable support and maintenance.

Thanks for letting us know, but given that I have stated numerous times
that I can not maintain 3 longterm stable kernels at the same time, and
if you look at the published supported schedule at:
	https://www.kernel.org/category/releases.html
it's going to be impossible for me to choose 3.13 as a longterm kernel,
sorry.

But best of luck with your LTS kernel, and if you find patches that are
applicable for 3.10, please feel free to send them to
stable@vger.kernel.org so that we can pick them up for that release as
well.

thanks,

greg k-h

      reply	other threads:[~2013-11-21 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 23:42 Leann Ogasawara
2013-11-21 17:30 ` Greg KH [this message]

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=20131121173002.GB21986@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=leann.ogasawara@canonical.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

all inboxes | Powered by JetHome®