summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorThomas Weißschuh <linux@weissschuh.net>2023-10-03 08:30:03 +0200
committerJonathan Corbet <corbet@lwn.net>2023-10-10 13:58:54 -0600
commit1fae02e7eb99fa8feba18ce444d8ce3546e6010e (patch)
tree215a8fa62adff8af310f0059e8224468c97f45f7 /Documentation
parentf1477dbfa5623a2738dbee77f4453f4d2519a103 (diff)
downloadlinux-stable-1fae02e7eb99fa8feba18ce444d8ce3546e6010e.tar.gz
linux-stable-1fae02e7eb99fa8feba18ce444d8ce3546e6010e.tar.bz2
linux-stable-1fae02e7eb99fa8feba18ce444d8ce3546e6010e.zip
docs: submitting-patches: encourage direct notifications to commenters
Commenters may not receive new versions of patches via the lists. Without a directed notification to them they might miss those new versions. This is frustrating for the patch developers as they don't receive their earned Reviewed-by. It is also frustrating for the commenters, as they might think their review got ignored or they have to dig up new versions from the archive manually. So encourage patch submitters to make sure that all commenters get notified also when no Reviewed-by was issued yet. Signed-off-by: Thomas Weißschuh <linux@weissschuh.net> Reviewed-by: Christoph Hellwig <hch@lst.de> Acked-by: Alexander Dahl <ada@thorsis.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20231003-docs-cc-reviewer-v2-1-f93fb946e21e@weissschuh.net
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/process/submitting-patches.rst2
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index 3fcfa029c9b3..86d346bcb8ef 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -327,6 +327,8 @@ politely and address the problems they have pointed out. When sending a next
version, add a ``patch changelog`` to the cover letter or to individual patches
explaining difference against previous submission (see
:ref:`the_canonical_patch_format`).
+Notify people that commented on your patch about new versions by adding them to
+the patches CC list.
See Documentation/process/email-clients.rst for recommendations on email
clients and mailing list etiquette.