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.