lkml.org 
[lkml]   [2010]   [Dec]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Announcement: Plans for v2.6.34-longterm
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.

Other than that, good luck with this, it's a lot of work :)

greg k-h


\
 
 \ /
  Last update: 2010-12-04 18:31    [W:0.128 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site