Thomas Weißschuh <linux@xxxxxxxxxxxxxx> writes: > 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@xxxxxxxxxxxxxx> > --- > Changes in v2: > - s/reviewer/commenter/ to avoid ambiguity (Christoph) > - Link to v1: https://lore.kernel.org/r/20230927-docs-cc-reviewer-v1-1-2af46ceb2d3c@xxxxxxxxxxxxxx > --- > 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..3245b7b38b98 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. Applied, thanks. jon
