Re: [PATCH] MyFirstContribution: leave a blank line between mailing-list paragraphs
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 18, 2026, 18:35 UTC
- Message-ID
- <xmqqy0aq56oj.fsf@gitster.g>
- In-Reply-To
- <20261118105227.50447-1-okhuomonajayi54@gmail.com>
Okhuomon Ajayi <okhuomonajayi54@gmail.com> writes:
Show 14 quoted lines
> diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc > index c58253fd54..9c189b6c9e 100644 > --- a/Documentation/MyFirstContribution.adoc > +++ b/Documentation/MyFirstContribution.adoc > @@ -1357,6 +1357,9 @@ relevant to your response. It is usually helpful to trim away unrelated context, > such as large portions of the patch that are not being discussed, while keeping > enough quoted text for readers to understand what you are responding to. > > +Leave a blank line between paragraphs. A block of quoted text counts > +as a paragraph, so leave a blank line before and after it. > + > Make sure your email client has a plaintext email mode and it is turned on; the > Git list rejects HTML email. Please also follow the mailing list etiquette > outlined in the
Sounds like a good way to help readability. I didn't expect this patch to extend MyFirstContribution, as the first chance for anybody has to deal with "quoted text" is when writing a response to other's patch during a review, not when responding to a review, but it seems that CodingGuidelines, Submittingpatches, and ReviewingGuidelines do not even talk about line length limit for e-mailed communications (which is a bit surprising).
Will queue. Thanks.