linux-kernel - Re: Stable -rc git trees and email headers

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: <5764CAFC.40802@roeck-us.net>
Date:	Fri, 17 Jun 2016 21:15:56 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Greg KH <gregkh@...uxfoundation.org>,
	Kevin Hilman <khilman@...libre.com>,
	Fengguang Wu <fengguang.wu@...el.com>
Cc:	stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Stable -rc git trees and email headers

Hi Greg,

On 06/17/2016 08:16 PM, Greg KH wrote:
> Hi,
>
> I've finally gotten off my butt and made my quilt trees of patches into
> a "semi-proper" git tree to make it easier for people to test them.
>
> I'm now pushing the patches I accept into the stable queues into the git
> tree here:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>
Great!

> I'll push them out in chunks, as I accept them, and when I do a "real"
> -rc release.  Right now the HEAD of each branch will have a -rc1 tag on
> them, just because it makes it a bit easier on my end.
>
> Note these branches WILL get rebased.  All the time.  So don't count on
> them to contain anything that will stick around, UNTIL a real stable
> release happens.
>
> Guenter, I hope this helps with your testing, is there anything that I
> can do here to make it easier for you?
>
Yes, it does. I'll see if I can switch to fetching the branches from there
in the next couple of days. I'm all happy ...

Thanks!

Guenter