Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Richard Kerry <richard.kerry@atos.ai>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Email formatting (was RE: [Outreachy] Draft internship proposal: Improve how command arguments and options are scanned and parsed)
Date: Tue, 17 Nov 2026 09:47:14 -0800	[thread overview]
Message-ID: <xmqqik1vfizh.fsf@gitster.g> (raw)
In-Reply-To: <AS4PR02MB83363999DA64DD82F6E25FB0EB7B2@AS4PR02MB8336.eurprd02.prod.outlook.com> (Richard Kerry's message of "Tue, 17 Nov 2026 09:41:46 +0000")

Richard Kerry <richard.kerry@atos.ai> writes:

> I don't know whether it's because of my mail reader, which is
> Outlook (I know it isn't a favourite in these parts but this is a
> corporate machine), but this email has come through to me with no
> indentation and no blank lines between any lines.
>
> I don't know whether the guidelines explicitly mention this but
> for myself I find both these properties make it difficult to read.
>
> There are a small number of fairly frequent contributors to the
> list who are also in the habit of not putting blank lines around
> additions (or even putting just one after the addition) within
> long blocks of text with reply marks (ie '>' characters).  That
> also doesn't help me be able to easily read contributions.  If
> there is a mass of text with all but a handful of lines starting
> with '>' they are very difficult to spot.
>
> Would it be reasonable for me to ask that the guidelines should
> request at least a little bit of breaking of large slabs of text,
> whether plain text, as here, or long replies, as elsewhere?

We do tell our folks that all text (commit log messages, code,
documentation sources and e-mail communications) must be
line-wrapped to comfortably fit on an 80-column terminal after
getting "> quoted" a few times in the discussion exchange, which
means that the practical limit is around 70 columns [jc: I
line-wrapped your message above as you sent four long lines, with a
blank line between each pair].

I do prefer to see a blank line between paragraphs, and here
"paragraph" includes a block of "> quoted" text, so I do not mind if
somebody adds to the documentation near where we talk about the
line-length limit and line-wrapping such a rule.

Thanks for raising the issue.

  reply	other threads:[~2026-11-17 17:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  5:21 [Outreachy] Draft internship proposal: Improve how command arguments and options are scanned and parsed Fien Dora
2026-11-17  9:41 ` Email formatting (was RE: [Outreachy] Draft internship proposal: Improve how command arguments and options are scanned and parsed) Richard Kerry
2026-11-17 17:47   ` Junio C Hamano [this message]
2026-11-17 18:20     ` 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=xmqqik1vfizh.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=richard.kerry@atos.ai \
    /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