[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <963811ba-6c12-47d1-942e-ba7bcf93a766@leemhuis.info>
Date: Thu, 11 Apr 2024 07:50:29 +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 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
Ciao, Thorsten
Powered by blists - more mailing lists