[PATCH v2 0/2] doc: clarify review replies and reroll timing

Hi,

This small series updates the 2 documentations: MyFirstContribution and SubmittingPatches.

The first patch clarifies that review feedback should not be answered only by sending a new version of the patches, which is talked in [1]. Contributors are encouraged to and should discuss their planned response in the existing review thread, so that the next version does not become the only place where reviewers can infer the author's reasoning.

The second patch is originally from an email from Patrick [2], which documents a rough expectation around reroll frequency.

Patrick suggests: There is no hard rule for when to send a new version, but batching feedback and avoiding multiple rerolls of the same series in a single day is a useful default. The text also mentions factors that may affect this, such as the size of the series, the depth of review, and whether the topic is close to being picked up.

Since I am the newbie here, please tell me how to attribute the credit to Patrick. Thank you Patrick!

Please feel free to make comments. Thank you.

[1]: <xmqq7bo5nf31.fsf@gitster.g> [2]: <aietF4BX1Ewt3cpG@pks.im>

---

Changes in v2:

For [PATCH 1/2] doc: encourage review replies before rerolling:

  - Add "social interactions" in commit message.

I didn't do any changes to this version for Patrick's comments in [a]:

Thinking about whether to delete/revert or not. Comments welcome.

For [PATCH 2/2] doc: advise batching patch rerolls:

  - Add a trailer to thank Patrick.

  Suggestions from Junio:

  - Mention that waiting between rerolls gives reviewers across time
    zones a fair chance to participate.
  - Mention that waiting also encourages authors to polish patches
    before sending them.

[a] <ai_7Wh7hrD8PZozg@pks.im>

--- base commit: 700432b2ba (topic flush before -rc1 (batch 1), 2026-06-15)

Weijie Yuan (2):
  doc: encourage review replies before rerolling
  doc: advise batching patch rerolls

 Documentation/MyFirstContribution.adoc | 32 ++++++++++++++++++++++----
 Documentation/SubmittingPatches        | 22 ++++++++++++++----
 2 files changed, 45 insertions(+), 9 deletions(-)

Range-diff against v1:
1:  b9fa5fe471 ! 1:  4bb1efe71d doc: encourage review replies before rerolling
    @@ Commit message
     
         This makes the author's reasoning explicit before the next version is
         prepared, instead of forcing reviewers to infer it from the rerolled
    -    patches.
    +    patches. It also encourages more direct social interaction between
    +    contributors and helps foster a more collaborative review process.
     
         Signed-off-by: Weijie Yuan <wy@wyuan.org>
     
2:  fafec6b31d ! 2:  496a08c74d doc: advise batching patch rerolls
    @@ Commit message
         Contributors often need guidance on how quickly to send later iterations
         of a patch series. Add a rough default of no more than one new version
         of the same series per day so feedback can be batched and reviewers have
    -    time to comment.
    +    time to comment regardless of their time zones.
     
         Mention factors that can affect the timing, such as series size, review
         depth, substantial rework, and how close the topic is to being accepted.
    +    Also point out that avoiding rapid rerolls encourages authors to polish
    +    each version before sending it, so reviewers can focus on substantial
    +    issues.
     
    +    Helped-by: Patrick Steinhardt <ps@pks.im>
         Signed-off-by: Weijie Yuan <wy@wyuan.org>
     
      ## Documentation/MyFirstContribution.adoc ##
    @@ Documentation/MyFirstContribution.adoc: previous one" patches over 2 days), revi
      single polished version came 2 days later instead, and that version with
      fewer mistakes were the only one they would need to review.
      
    -+This consideration applies not only when going from the initial patch to v2, but
    -+also to later iterations of the same series. There is no fixed rule for how long
    -+to wait before sending a new version. A useful default is to send at most one
    -+new version of the same patch series per day. This gives multiple reviewers time
    -+to comment, lets you batch feedback together, and gives you time to think
    -+through the comments you received.
    ++This consideration applies not only when going from the initial patch to v2,
    ++but also to later iterations of the same series. There is no fixed rule for how
    ++long to wait before sending a new version. A useful default is to send at most
    ++one new version of the same patch series per day. This gives multiple reviewers
    ++time to comment, gives reviewers across time zones a fair chance to
    ++participate, lets you batch feedback together, and gives you time to think
    ++through the comments you received. Knowing that you should not immediately send
    ++another version also encourages you to review the patches more carefully before
    ++sending them, catch small mistakes such as typos and off-by-one errors
    ++yourself, and let reviewers spend more of their attention on design,
    ++algorithms, and other substantial issues.
     +
     +The right timing depends on the topic and the feedback. Larger series usually
     +need more review time. If the only comments so far are minor, such as typo
    @@ Documentation/MyFirstContribution.adoc: previous one" patches over 2 days), revi
      === Responding to Reviews
     
      ## Documentation/SubmittingPatches ##
    -@@ Documentation/SubmittingPatches: It is often beneficial to allow some time for reviewers to provide
    +@@ Documentation/SubmittingPatches: area.
    + It is often beneficial to allow some time for reviewers to provide
      feedback before sending a new version, rather than sending an updated
      series immediately after receiving a review. This helps collect broader
    - input and avoids unnecessary churn from many rapid iterations.
    +-input and avoids unnecessary churn from many rapid iterations.
    ++input, gives reviewers in different time zones a fair chance to comment,
    ++and avoids unnecessary churn from many rapid iterations.  Waiting also
    ++encourages you to polish each version before sending it, so reviewers can
    ++focus on substantial issues rather than typos or other small mistakes.
     ++
     +As a rough default, avoid sending more than one new version of the same
     +series per day, while considering the size of the series, the depth of