From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Sasha Levin <sashal@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
stable@vger.kernel.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] docs: stable-kernel-rules: create special tag to flag 'no backporting'
Date: Mon, 29 Apr 2024 09:51:40 +0200 [thread overview]
Message-ID: <2024042914-bleep-imbecile-5f68@gregkh> (raw)
In-Reply-To: <35989d3b2f3f8cf23828b0c84fde9b17a74be97c.1714367921.git.linux@leemhuis.info>
On Mon, Apr 29, 2024 at 09:18:30AM +0200, Thorsten Leemhuis wrote:
> Document a new variant of the stable tag developers can use to make the
> stable team's tools ignore a change[1].
>
> That way developers can use 'Fixes:' tags without fearing the changes
> might be backported in semi-automatic fashion. Such concerns are the
> reason why some developers deliberately omit the 'Fixes:' tag in
> changes[2] -- which somewhat undermines the reason for the existence of
> that tag and might be unwise in the long term[3].
>
> Link: https://lore.kernel.org/all/b452fd54-fdc6-47e4-8c26-6627f6b7eff3@leemhuis.info/ [1]
> Link: https://lore.kernel.org/all/cover.1712226175.git.antony.antony@secunet.com/ [2]
> Link: https://lore.kernel.org/all/dfd87673-c581-4b4b-b37a-1cf5c817240d@leemhuis.info/ [3]
> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
>
> ---
>
> A patch to make one of the stable-script honor the flag can be found in
> https://lore.kernel.org/all/655ce2a3-eb04-4ade-999e-23fc5dc5fb3a@leemhuis.info/
>
> For autosel I was unable to locate the code.
> ---
> Documentation/process/stable-kernel-rules.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
> index ebf4152659f2d0..9ca8083b41c7f1 100644
> --- a/Documentation/process/stable-kernel-rules.rst
> +++ b/Documentation/process/stable-kernel-rules.rst
> @@ -129,6 +129,12 @@ comment to pass arbitrary or predefined notes:
>
> Cc: <stable@vger.kernel.org> # see patch description, needs adjustments for <= 6.3
>
> +There furthermore is a variant of the stable tag you can use to make the stable
> +team's backporting tools (e.g AUTOSEL or scripts that look for commits
> +containing a 'Fixes:' tag) ignore a change::
> +
> + Cc: <stable+noautosel@kernel.org> # reason goes here, and must be present
> +
> .. _option_2:
>
Thanks for seeing this through:
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2024-04-29 7:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 7:18 [PATCH v2 0/5] docs: stable-kernel-rules: fine-tuning and 'no stable backport' tag Thorsten Leemhuis
2024-04-29 7:18 ` [PATCH v2 1/5] docs: stable-kernel-rules: reduce redundancy Thorsten Leemhuis
2024-04-29 7:18 ` [PATCH v2 2/5] docs: stable-kernel-rules: call mainline by its name and change example Thorsten Leemhuis
2024-04-29 7:49 ` Greg Kroah-Hartman
2024-04-29 7:18 ` [PATCH v2 3/5] docs: stable-kernel-rules: remove code-labels tags and a indention level Thorsten Leemhuis
2024-04-29 7:49 ` Greg Kroah-Hartman
2024-04-29 7:18 ` [PATCH v2 4/5] docs: stable-kernel-rules: explain use of stable@kernel.org (w/o @vger.) Thorsten Leemhuis
2024-04-29 7:51 ` Greg Kroah-Hartman
2024-04-29 8:30 ` Thorsten Leemhuis
2024-04-29 8:36 ` Greg Kroah-Hartman
2024-04-29 7:18 ` [PATCH v2 5/5] docs: stable-kernel-rules: create special tag to flag 'no backporting' Thorsten Leemhuis
2024-04-29 7:51 ` Greg Kroah-Hartman [this message]
2024-05-02 16:13 ` [PATCH v2 0/5] docs: stable-kernel-rules: fine-tuning and 'no stable backport' tag Jonathan Corbet
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=2024042914-bleep-imbecile-5f68@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).