All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Thomas Weißschuh" <linux@weissschuh.net>
Subject: [PATCH] docs: submitting-patches: encourage direct notifications to reviewers
Date: Wed, 27 Sep 2023 20:52:21 +0200	[thread overview]
Message-ID: <20230927-docs-cc-reviewer-v1-1-2af46ceb2d3c@weissschuh.net> (raw)

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@weissschuh.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@weissschuh.net>


             reply	other threads:[~2023-09-27 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 18:52 Thomas Weißschuh [this message]
2023-09-28  9:13 ` [PATCH] docs: submitting-patches: encourage direct notifications to reviewers Christoph Hellwig
2023-09-28  9:17   ` Laurent Pinchart
2023-09-29  7:24   ` Thomas Weißschuh
2023-10-02  6:34     ` Christoph Hellwig
2023-10-02  7:36       ` Jani Nikula
2023-10-02  8:50         ` Christoph Hellwig
2023-10-02 17:04           ` Thomas Weißschuh

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=20230927-docs-cc-reviewer-v1-1-2af46ceb2d3c@weissschuh.net \
    --to=linux@weissschuh.net \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.