git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Email formatting (was RE: [Outreachy] Draft internship proposal: Improve how command arguments and options are scanned and parsed)

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 17, 2026, 17:47 UTC
Message-ID
<xmqqik1vfizh.fsf@gitster.g>
In-Reply-To
<AS4PR02MB83363999DA64DD82F6E25FB0EB7B2@AS4PR02MB8336.eurprd02.prod.outlook.com>
Richard Kerry <richard.kerry@atos.ai> writes:
Show 19 quoted lines
> 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.
Previous: Richard KerryNext: Okhuomon Ajayi
Message 3 of 5 in “[Outreachy] Draft internship proposal: Improve how command arguments and options are scanned and parsed”
  1. Fien DoraNov 9, 2026
  2. Email formatting (was RE: [Outreachy] Draft internship proposal: Improve how command arguments and options are scanned and parsed)Richard Kerry, Nov 17, 2026
  3. Junio C HamanoNov 17, 2026
  4. Okhuomon AjayiNov 17, 2026
  5. MyFirstContribution: leave a blank line between mailing-list paragraphsOkhuomon Ajayi, Nov 17, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.