From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org, regressions@lists.linux.dev,
linux-doc@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1 4/6] docs: 6.Followthrough.rst: tags to use in regressions fixes
Date: Fri, 20 Dec 2024 14:18:11 +0100 [thread overview]
Message-ID: <13cc09ff-1a4c-46bf-941c-ddc28e60b0ce@leemhuis.info> (raw)
In-Reply-To: <87a5czwnxv.fsf@trenco.lwn.net>
On 13.12.24 17:24, Jonathan Corbet wrote:
> Thorsten Leemhuis <linux@leemhuis.info> writes:
> [...]
>> diff --git a/Documentation/process/6.Followthrough.rst b/Documentation/process/6.Followthrough.rst
>> index 763a80d21240f0..2ba16a71aba9b4 100644
>> --- a/Documentation/process/6.Followthrough.rst
>> +++ b/Documentation/process/6.Followthrough.rst
>> @@ -234,6 +234,22 @@ On procedure:
>> requests again should ideally come directly from maintainers or happen in
>> accordance with them.
> [...]
>> + - Did the culprit make it into a proper mainline release during the past
>> + twelve months? Or is it a recent mainline commit backported to stable or
>> + longterm releases in the past few weeks? Then you are kindly asked to ensure
>> + stable inclusion as described by Documentation/process/stable-kernel-rules.rst.
>> + Usually you want to realized thos by adding a "Cc: stable@vger.kernel.org" to
>
> Something went a bit astray in that sentence. "you want to do this" ?
Uhhps, yeah, went with 'Many developers realize this by adding a "Cc:
stable@vger.kernel.org" to the patch description.'. That also leaves...
>> + the patch description. Note, a "Fixes:" tag alone does not guarantee a
>> + backport, as the stable team does not pick up all such changes and might
>> + silently drop them in case trouble arises.
>
> In the past we have had subsystem maintainers who didn't want people to
> put CC: stable tags into their own patches; not sure if that's still the case?
...it somewhat open for such subsystems, if there still are any.
Ciao, Thorsten
next prev parent reply other threads:[~2024-12-20 13:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 10:15 [PATCH v1 0/6] docs: add instruction about handling regressions to our core texts for contributors Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 1/6] docs: more detailed instructions on handling regressions Thorsten Leemhuis
2024-12-13 16:14 ` Jonathan Corbet
2024-12-20 12:17 ` Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 2/6] docs: 6.Followthrough.rst: when to involved Linus in regressions Thorsten Leemhuis
2024-12-13 16:17 ` Jonathan Corbet
2024-12-20 12:41 ` Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 3/6] docs: 6.Followthrough.rst: interaction with stable wrt to regressions Thorsten Leemhuis
2024-12-13 16:20 ` Jonathan Corbet
2024-12-20 13:13 ` Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 4/6] docs: 6.Followthrough.rst: tags to use in regressions fixes Thorsten Leemhuis
2024-12-13 16:24 ` Jonathan Corbet
2024-12-20 13:18 ` Thorsten Leemhuis [this message]
2024-12-10 10:15 ` [PATCH v1 5/6] docs: 6.Followthrough.rst: more specific advice on fixing regressions Thorsten Leemhuis
2024-12-13 16:28 ` Jonathan Corbet
2024-12-20 14:21 ` Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 6/6] docs: 6.Followthrough.rst: advice on handling regressions fixes Thorsten Leemhuis
2024-12-13 16:30 ` Jonathan Corbet
2024-12-20 14:24 ` Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13cc09ff-1a4c-46bf-941c-ddc28e60b0ce@leemhuis.info \
--to=linux@leemhuis.info \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox