linux-kernel - Re: [ 3.8.y.z extended stable ] Linux 3.8.13.11 stable review

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: <1382059831.2794.18.camel@deadeye.wl.decadent.org.uk>
Date:	Fri, 18 Oct 2013 02:30:31 +0100
From:	Ben Hutchings <ben@...adent.org.uk>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Kamal Mostafa <kamal@...onical.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	kernel-team@...ts.ubuntu.com,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Luis Henriques <luis.henriques@...onical.com>
Subject: Re: [ 3.8.y.z extended stable ] Linux 3.8.13.11 stable review

On Thu, 2013-10-10 at 11:37 -0600, Bjorn Helgaas wrote:
> On Thu, Oct 10, 2013 at 9:40 AM, Kamal Mostafa <kamal@...onical.com> wrote:
> > This is the start of the review cycle for the Linux 3.8.13.11 stable kernel.
> 
> Would anybody be interested in adding some sort of "stable" tag to the
> subject lines of stable backport patches, e.g.,  instead of:
> 
>   [PATCH 001/104] htb: fix sign extension bug
> 
> something like:
> 
>   [STABLE 3.8.13.11 001/104] htb: fix sign extension bug
> 
> I don't mind having the stable patches on LKML, but it would be nice
> if it were easier to distinguish stable backports from new patches.  I
> know the patches are nicely threaded behind this message, but some
> readers don't really pay attention to that.

I agree that some distinction is needed, but I'm not convinced about
that precise format.  I don't think it's worth including version
components after the stable base version e.g. 3.2.  And I think that
including the version is a big enough clue that this is for a stable
branch and not mainline.

So I've changed my review script to put a subject prefix of 'PATCH 3.2'
before the patch number (and similarly in the cover letter).  But if
there's consensus that a more explicit tag is wanted then I'll follow
that.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
                   Among economists, the real world is often a special case.

Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)