linux-kernel - Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example

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: Thu, 11 Apr 2024 09:18:26 +0200
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Sasha Levin <sashal@...nel.org>, Jonathan Corbet <corbet@....net>,
 stable@...r.kernel.org, workflows@...r.kernel.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its
 name and change example

On 11.04.24 08:56, Greg Kroah-Hartman wrote:
> On Thu, Apr 11, 2024 at 08:50:19AM +0200, Thorsten Leemhuis wrote:
>> On 11.04.24 08:10, Greg Kroah-Hartman wrote:
>>> On Thu, Apr 11, 2024 at 07:50:29AM +0200, Thorsten Leemhuis wrote:
>>>> On 11.04.24 07:30, Greg Kroah-Hartman wrote:
>>>>> On Thu, Apr 11, 2024 at 07:25:05AM +0200, Thorsten Leemhuis wrote:
>>>>>>  
>>>>>> -     Cc: <stable@...r.kernel.org> # after 4 weeks in mainline
>>>>>> +     Cc: <stable@...r.kernel.org> # after 6 weeks in a stable mainline release
> 
> So how about changing it to use the "fixed point" reference please?  The
> phrasing "after -rc3" is probably what most people almost always want
> anyway, given the huge churn that -rc1 is.

Okay, will go with that phrase in v2; people that want to express "four
weeks after the change hit a proper mainline release" (I've seen a few
people want something like that to ensure it gets field testing in a
real release) can then add a version number to it.

Thx! Ciao, Thorsten