From: Junio C Hamano <gitster@pobox.com>
To: Okhuomon Ajayi <okhuomonajayi54@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] MyFirstContribution: leave a blank line between mailing-list paragraphs
Date: Wed, 18 Nov 2026 10:35:24 -0800 [thread overview]
Message-ID: <xmqqy0aq56oj.fsf@gitster.g> (raw)
In-Reply-To: <20261118105227.50447-1-okhuomonajayi54@gmail.com> (Okhuomon Ajayi's message of "Wed, 18 Nov 2026 11:52:27 +0100")
Okhuomon Ajayi <okhuomonajayi54@gmail.com> writes:
> 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.
next prev parent reply other threads:[~2026-11-18 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 10:52 [PATCH] MyFirstContribution: leave a blank line between mailing-list paragraphs Okhuomon Ajayi
2026-11-18 18:35 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-17 18:20 Email formatting (was RE: [Outreachy] Draft internship proposal: Improve how command arguments and options are scanned and parsed) Okhuomon Ajayi
2026-11-17 18:49 ` [PATCH] MyFirstContribution: leave a blank line between mailing-list paragraphs Okhuomon Ajayi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy0aq56oj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=okhuomonajayi54@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox