From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Greg KH <greg@kroah.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: Sat, 4 Dec 2010 19:45:54 -0500 [thread overview]
Message-ID: <20101205004554.GA314@windriver.com> (raw)
In-Reply-To: <20101204172718.GB10282@kroah.com>
[Re: Announcement: Plans for v2.6.34-longterm] On 04/12/2010 (Sat 09:27) Greg KH wrote:
> On Fri, Dec 03, 2010 at 04:07:19PM -0500, Paul Gortmaker wrote:
> > Firstly, I'd like to thank Greg for all the past work he's done on
> > juggling all these different stable releases - many people have
> > reaped the benefits of them for quite some time, and it only makes
> > sense to spread the loading around as it has grown significantly.
> >
> > 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.
> >
> > I've already done an end-to-end audit of the current 2.6.32 longterm
> > stable release, and used the list of these already "approved for stable"
> > patches on v2.6.32 to identify 260 upstream commits that are applicable,
> > but not yet present in the last 2.6.34.7 stable release.
> >
> > A candidate tree for 2.6.34.8 with the above 260 commits applied to
> > it is available now for review/testing at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-2.6.34.y.git
>
> That's great, but you really don't want to keep the patches in a
> "combined" git tree like this for development and review. What happens
> if someone says "patch 121 needs to be removed"?
>
> I recommend using quilt like we have been for the stable tree for the
> past 5+ years as it handles situations like this very well.
It was my intention to also create a git repo of patches, but since I've
found myself using quilt less and less in favour of just using git
directly, it wasn't a natural byproduct of my work so far.
Fortunately its easy to dump patches out into a repo of patches suitable
for quilt, so there is one now, and it makes a good place to put that
audit data relating to this that I'd sent you a couple weeks ago.
http://git.kernel.org/?p=linux/kernel/git/paulg/stable-queue.git;a=summary
> Other than that, good luck with this, it's a lot of work :)
Thanks!
Paul.
>
> greg k-h
next prev parent reply other threads:[~2010-12-05 0:46 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 [this message]
2010-12-04 17:28 ` Greg KH
2010-12-05 1:16 ` Paul Gortmaker
2010-12-05 16:50 ` Greg KH
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=20101205004554.GA314@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=greg@kroah.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox