On 23/07/27 05:43PM, Junio C Hamano wrote: > Finding mistakes in and improving your own patches is a good idea, > but doing so too quickly is being inconsiderate to reviewers who > have just seen the initial iteration and taking their time to review > it. Encourage new developers to perform such a self review before > they send out their patches, not after. After sending a patch that > they immediately found mistakes in, they are welcome to comment on > them, mentioning what and how they plan to improve them in an > updated version, before sending out their updates. > > [...] > > +Please be considerate of the time needed by reviewers to examine each > +new version of your patch. Rather than seeing the initial version right > +now (followed by several "oops, I like this version better than the > +previous one" patches over 2 days), reviewers would strongly prefer if a > +single polished version came 2 days later instead, and that version with > +fewer mistakes were the only one they would need to review. > + > + > [...] Speaking as a fairly green contributor to the project, it may be helpful to include some guidance on what is "too long" vs "too short" when waiting to send out the next revision. Likewise it may be worthwhile to mention how the expected "minimum time between revisions" will generally shrink as you get to higher revision counts and fewer changes between revisions.
