workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	stable@vger.kernel.org, workflows@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
Date: Thu, 11 Apr 2024 07:25:04 +0200	[thread overview]
Message-ID: <c0a08b160b286e8c98549eedb37404c6e784cf8a.1712812895.git.linux@leemhuis.info> (raw)
In-Reply-To: <cover.1712812895.git.linux@leemhuis.info>

Some developers deliberately steer clear of 'Fixes:' tags to prevent
changes from being backported semi-automatically by the stable team.
That somewhat undermines the reason for the existence of the Fixes: tag,
hence point out there is an alternative to reach the same effect.

Link: https://lore.kernel.org/all/dfd87673-c581-4b4b-b37a-1cf5c817240d@leemhuis.info/
Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
---
 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 7bb16d42a51833..ebd57cb9277f7b 100644
--- a/Documentation/process/stable-kernel-rules.rst
+++ b/Documentation/process/stable-kernel-rules.rst
@@ -117,6 +117,12 @@ comment to pass arbitrary or predefined notes:
    Note, such tagging is unnecessary if the stable team can derive the
    appropriate versions from Fixes: tags.
 
+ * Prevent semi-automatic backporting of changes carrying a 'Fixes:' tag:
+
+   .. code-block:: none
+
+     Cc: <stable@vger.kernel.org> # no semi-automatic backport
+
  * Delay pick up of patches:
 
    .. code-block:: none
-- 
2.44.0


  parent reply	other threads:[~2024-04-11  5:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  5:25 [PATCH v1 0/4] docs: stable-kernel-rules: fine-tuning and 'no semi-automatic backport' Thorsten Leemhuis
2024-04-11  5:25 ` [PATCH v1 1/4] docs: stable-kernel-rules: reduce redundancy Thorsten Leemhuis
2024-04-11  5:27   ` Greg Kroah-Hartman
2024-04-11  5:25 ` Thorsten Leemhuis [this message]
2024-04-11  5:29   ` [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport" Greg Kroah-Hartman
2024-04-11  6:59     ` Thorsten Leemhuis
2024-04-11  7:40       ` Greg Kroah-Hartman
2024-04-11  7:50         ` Thorsten Leemhuis
2024-04-11  9:13           ` Greg Kroah-Hartman
2024-04-11  9:19             ` Geert Uytterhoeven
2024-04-11  9:53               ` Greg Kroah-Hartman
2024-04-11  9:57               ` Thorsten Leemhuis
2024-04-11 15:12                 ` Greg Kroah-Hartman
2024-04-11  5:25 ` [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example Thorsten Leemhuis
2024-04-11  5:30   ` Greg Kroah-Hartman
2024-04-11  5:50     ` Thorsten Leemhuis
2024-04-11  6:10       ` Greg Kroah-Hartman
2024-04-11  6:50         ` Thorsten Leemhuis
2024-04-11  6:56           ` Greg Kroah-Hartman
2024-04-11  7:18             ` Thorsten Leemhuis
2024-04-11  5:25 ` [PATCH v1 4/4] docs: stable-kernel-rules: remove code-labels tags Thorsten Leemhuis
2024-04-11  5:31   ` Greg Kroah-Hartman

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=c0a08b160b286e8c98549eedb37404c6e784cf8a.1712812895.git.linux@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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