linux-kernel - Re: [Ksummit-2013-discuss] KS Topic request: Handling the Stable kernel, let's dump the cc: stable tag

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:	Mon, 15 Jul 2013 23:04:28 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	James Bottomley <James.Bottomley@...senPartnership.com>,
	ksummit-2013-discuss@...ts.linuxfoundation.org,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [Ksummit-2013-discuss] KS Topic request: Handling the Stable
 kernel, let's dump the cc: stable tag

On Mon, 2013-07-15 at 13:19 -0700, Guenter Roeck wrote:
> That seems to be a bit drastic. It is quite useful to have the tag,
> but maybe it should only be added by the maintainer and not in the initial
> patch submission. This would ensure that the maintainer(s) made the decision.
> If the original patch submitter thinks that the patch is stable material,
> that information could be added in the comments section.

In the case where a maintainer applies a patch with 'git am', surely
they can *see* that it's cc:stable?

-- 
dwmw2


Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5745 bytes)