All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@kernel.org,
	jason.wessel@windriver.com, Andi Kleen <andi@firstfloor.org>,
	lwn@lwn.net
Subject: Re: Announcement: Plans for v2.6.34-longterm
Date: Sun, 5 Dec 2010 08:50:34 -0800	[thread overview]
Message-ID: <20101205165034.GA15738@kroah.com> (raw)
In-Reply-To: <20101205011644.GB314@windriver.com>

On Sat, Dec 04, 2010 at 08:16:44PM -0500, Paul Gortmaker wrote:
> [Re: Announcement: Plans for v2.6.34-longterm] On 04/12/2010 (Sat 09:28) Greg KH wrote:
> 
> > On Fri, Dec 03, 2010 at 04:07:19PM -0500, Paul Gortmaker wrote:
> > > With that in mind, it is our intention to also maintain a 2.6.34
> > > longterm tree.  Jason and I work at Wind River, which already has
> > > released products based on v2.6.34, and as such it only makes sense
> > > to have a public long-term tree that others who are also based on
> > > 2.6.34 can make use of.
> > 
> > Other than Wind River, what other distros/userbases are using .34 as a
> > platform for their products?
> 
> Well, since we create more of a distro builder, than a distro itself,
> anyone who uses WR to in turn create a distro for their own hardware or
> product will of course be using 2.6.34.  The Yocto project is currently
> using the 2.6.34 kernel and I'm sure there are others I'm not
> immediately aware of.

I thought Yocto was going to be using .35, hence Andi and Tim's work to
get that one "longterm"?

Anyway, that's fine, I was just curious, thanks.

> > And how long do you expect to be maintaining this .34 branch for?
> 
> The expectation is that maintenance will be ongoing for years, since
> we'll largely be needing to do that work anyway.  I plan to follow your
> lead on how you handled .27 -- i.e. the "early" releases will possibly
> be rich with content, but as it gets to be closer to EOL (i.e. on the
> order of 10 releases removed from current), then it will only be the key
> CVE-like fixes and similar which will be added.

That sounds very reasonable.

If there's anything I can do to help out, let me know.

thanks,

greg k-h

  reply	other threads:[~2010-12-05 17:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 21:07 Announcement: Plans for v2.6.34-longterm Paul Gortmaker
2010-12-04 17:27 ` Greg KH
2010-12-05  0:45   ` Paul Gortmaker
2010-12-04 17:28 ` Greg KH
2010-12-05  1:16   ` Paul Gortmaker
2010-12-05 16:50     ` Greg KH [this message]
2010-12-06  4:54       ` Bruce Ashfield
2010-12-06  5:35   ` Minchan Kim
2010-12-06  6:01     ` Minchan Kim
2011-11-08 22:14 ` George G. Davis
2011-11-08 23:11   ` Paul Gortmaker
2011-11-08 23:52     ` Greg KH
2011-11-09  3:20       ` Paul Gortmaker
2011-11-10 19:54         ` Greg KH
2011-11-10 20:29           ` Paul Gortmaker
2011-11-09 17:12     ` George G. Davis

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=20101205165034.GA15738@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=paul.gortmaker@windriver.com \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.