linux-kernel - Re: Announcement: Plans for v2.6.34-longterm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101204172718.GB10282@kroah.com>
Date:	Sat, 4 Dec 2010 09:27:18 -0800
From:	Greg KH <greg@...ah.com>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, stable@...nel.org,
	jason.wessel@...driver.com, Andi Kleen <andi@...stfloor.org>,
	lwn@....net
Subject: Re: 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/