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 v2 4/5] docs: stable-kernel-rules: explain use of stable@kernel.org (w/o @vger.)
Date: Mon, 29 Apr 2024 09:18:29 +0200 [thread overview]
Message-ID: <6783b71da48aac5290756343f58591dc42da87bc.1714367921.git.linux@leemhuis.info> (raw)
In-Reply-To: <cover.1714367921.git.linux@leemhuis.info>
Document when to use of stable@kernel.org instead of
stable@vger.kernel.org, as the two are easily mixed up and their
difference not explained anywhere[1].
Link: https://lore.kernel.org/all/20240422231550.3cf5f723@sal.lan/ [1]
Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
---
Documentation/process/stable-kernel-rules.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
index b4af627154f1d8..ebf4152659f2d0 100644
--- a/Documentation/process/stable-kernel-rules.rst
+++ b/Documentation/process/stable-kernel-rules.rst
@@ -72,6 +72,10 @@ for stable trees, add this tag in the sign-off area::
Cc: stable@vger.kernel.org
+Use ``Cc: stable@kernel.org`` instead when fixing unpublished vulnerabilities:
+it reduces the chance of accidentally exposing the fix to the public by way of
+'git send-email', as mails sent to that address are not delivered anywhere.
+
Once the patch is mainlined it will be applied to the stable tree without
anything else needing to be done by the author or subsystem maintainer.
--
2.44.0
next prev parent reply other threads:[~2024-04-29 7:18 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 ` Thorsten Leemhuis [this message]
2024-04-29 7:51 ` [PATCH v2 4/5] docs: stable-kernel-rules: explain use of stable@kernel.org (w/o @vger.) 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
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=6783b71da48aac5290756343f58591dc42da87bc.1714367921.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