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: <20160618052959.GA11059@1wt.eu>
Date:	Sat, 18 Jun 2016 07:29:59 +0200
From:	Willy Tarreau <w@....eu>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Kevin Hilman <khilman@...libre.com>,
	Guenter Roeck <linux@...ck-us.net>,
	Fengguang Wu <fengguang.wu@...el.com>, stable@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Stable -rc git trees and email headers

Hi Greg,

On Fri, Jun 17, 2016 at 08:16:20PM -0700, 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
> 
> 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.

Do you mean you'll tag them when you issue a review ? If so, maybe that
can help our testers automatically trigger a series of tests when they
spot a tag that was not tested yet instead of having to monitor emails ?
If that's the case, I have no issue with pushing a tag when I emit a
series as well.

Cheers,
Willy