linux-kernel - [PATCH] docs: submitting-patches: encourage direct notifications to reviewers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230927-docs-cc-reviewer-v1-1-2af46ceb2d3c@weissschuh.net>
Date:   Wed, 27 Sep 2023 20:52:21 +0200
From:   Thomas Weißschuh <linux@...ssschuh.net>
To:     Jonathan Corbet <corbet@....net>
Cc:     workflows@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Thomas Weißschuh <linux@...ssschuh.net>
Subject: [PATCH] docs: submitting-patches: encourage direct notifications
 to reviewers

Reviewers 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 reviewers, 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 reviewers get
notified also when no Reviewed-by was issued yet.

Signed-off-by: Thomas Weißschuh <linux@...ssschuh.net>
---
 Documentation/process/submitting-patches.rst | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index efac910e2659..8dca82dfcd69 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 reviewers and other involved people about new versions of your patch by
+adding them to the patches CC list.

 See Documentation/process/email-clients.rst for recommendations on email
 clients and mailing list etiquette.

---
base-commit: 633b47cb009d09dc8f4ba9cdb3a0ca138809c7c7
change-id: 20230926-docs-cc-reviewer-023b3730af23

Best regards,
-- 
Thomas Weißschuh <linux@...ssschuh.net>