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]

Message-ID: <2024041127-attach-removed-f9f0@gregkh>
Date: Thu, 11 Apr 2024 08:10:33 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Thorsten Leemhuis <linux@...mhuis.info>
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 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
> > 
> > I do not know what "stable mainline release" means here, sorry.  "after
> > 4 weeks in mainline" means "after in Linus's tree for 4 weeks, but
> > Linus's tree is not "stable mainline".
> 
> I meant a proper mainline release like 6.7 or 6.8 to make it obvious
> that this does not mean a "pre-release".
> 
> I actually had used the term "proper mainline release" earlier in a
> draft, but a quick search on the net showed that this is not really used
> out there. "stable mainline release" is not popular either, but seemed
> to be a better match; I also considered "final mainline release", but
> that felt odd.
> 
> It feels like there must be some better term my mind just stumbles to
> come up with. Please help. :-D

Well, what is the goal here?  Just put it in words, I have seen stuff
like:
	Cc: <stable@...r.kernel.org> # wait until -rc3
	Cc: <stable@...r.kernel.org> # wait until 6.1 is released
	Cc: <stable@...r.kernel.org> # after -rc2

and so on.

Just pick a specific time/release might be better?  "after X weeks" is
assuming that we all know and remember how many weeks something
happened...

thanks,

greg k-h