Junio C Hamano's patches respond to what he describes as a growing need for senior community members to tell new contributors not to send updated iterations before any review discussion on the current one. He says it is unclear how much of the blame belongs to the text, which currently explains how to send v1, then v2, and then how to respond to reviews.
The first version was a single patch that rewrote the "Reviewing" section and replaced the weak "it is a good manners to do so" with a firmer "do not send v2 before you are done". Patrick Steinhardt's review said it would have been easier to read if the text had been moved first without changes and reworded in a second commit, because it was hard to see what had moved. He also listed typos and extra blank lines. On the wording, he said it may be a bit broad, since he often explores ideas before he can properly respond to review feedback. But he added that being this firm may be justified by the recent trend of people not responding at all.
Junio's reroll splits the series. Patch 1/2 moves "how to send v2" after the review discussion, with no text changes, so it is easy to follow in git diff. Patch 2/2 consolidates the repeated cautions against sending updates too quickly into one passage, mixed with the new text.
Junio said he would do so again after sleeping on the topic for a few days and seeing other comments.