[PATCH v2 4/5] docs: stable-kernel-rules: explain use of stable@xxxxxxxxxx (w/o @vger.)

[Thorsten Leemhuis]

Document when to use of stable@xxxxxxxxxx instead of
stable@xxxxxxxxxxxxxxx, as the two are easily mixed up and their
difference not explained anywhere[1].

Link: https://lore.kernel.org/all/20240422231550.3cf5f723@xxxxxxx/ [1]
Signed-off-by: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
---
 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@xxxxxxxxxxxxxxx
 
+Use ``Cc: stable@xxxxxxxxxx`` 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