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]

Date:	Tue, 8 Nov 2011 15:52:56 -0800
From:	Greg KH <greg@...ah.com>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	"George G. Davis" <gdavis@...sta.com>,
	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 Tue, Nov 08, 2011 at 06:11:45PM -0500, Paul Gortmaker wrote:
> On 11-11-08 05:14 PM, George G. Davis wrote:
> > Greetings,
> > 
> 
> [...]
> 
> > 
> > Are there any plans to continue maintenance of v2.6.34-longterm now that
> > kernel.org is back online?
> 
> Yes,  in fact I have a queue ready for review shortly.  However I didn't
> want to overtax the kernel.org maintainers with nagging questions about
> longterm/stable directory layout & restoration -- as I'm sure they had more
> than their hands full with getting people back on the server and getting
> stuff functional for the merge window which just closed yesterday.

Ah, I'll handle this :)

So, in talking with Andi, we decided that I would just keep the "main"
linux-stable.git tree on kernel.org.  When you do a new release, I'll
merge that into the linux-stable.git tree and do the "official" tarball
release with the proper stable kernel signing key.

This should make your life a whole lot easier, just clone the existing
linux-stable.git tree, add your releases to the proper branch, and do a
pull request to me when you have it all ready to go.

It also makes managing things on the kernel.org side easier with
permissions and the like, as sharing a git tree can get messy as we've
seen in the past.

Sound reasonable?

Also, I would like to populate the linux-stable.git tree with the
missing .34-longterm releases that you have already done, care to
provide a git tree that I can pull from for those now?

Oh, you will need a kernel.org account for this, but I'm assuming that
you already have that set up, right?  If not, please do that first and
if you have any problems with it, let me know.

thanks,

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/