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

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

From
RKRichard Kerry <richard.kerry@atos.ai>
Date
Nov 17, 2026, 09:41 UTC
Message-ID
<AS4PR02MB83363999DA64DD82F6E25FB0EB7B2@AS4PR02MB8336.eurprd02.prod.outlook.com>
In-Reply-To
<CACWAS-UqbkgfzsJ2283=OgoUHRs-FeRNYc0zkBR2y0XD4jTWsw@mail.gmail.com>
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?

Regards, Richard.

Kind regards,

Richard Kerry BNCS Engineer - Media Competency Centre MidCity Place, 71 High Holborn - London WC1V 6EA - UK atos.ai

Show 29 quoted lines
> -----Original Message-----
> Sent: 09 November 2026 05:22
> Subject: [Outreachy] Draft internship proposal: Improve how command
> arguments and options are scanned and parsed
>
>
> Community: Git
> Project: Improve how command arguments and options are scanned and parsed
> Mentors: Christian Couder and Siddharth Asthana Internship period: December 7,
> 2026 - March 8, 2027 1. About Me Hello everyone, I'm Fien Dora, a Computer
> Engineer with an interest in C programming, systems programming, and
> understanding how things work in the background.
> I've always enjoyed mathematics and solving problems. I've always been curious
> about compilers, and what happens when a command is sent. That curiosity
> pushed me to start learning programming. In 2023, I joined the ALX learning
> program, where I was introduced to C, shell scripting, and systems programming.
> Of everything I was learning, C caught my attention the most.
> I liked that C helped me understand what was happening closer to the computer
> itself like compilers, interpreters, memory, and how software communicates with
> hardware.
> I am still growing as a C programmer, especially when it comes to understanding
> large codebases, but I enjoy taking time to understand a problem and working
> through it until things become clearer.
> That is one of the reasons I was drawn to Git's Outreachy project.
> Availability: 30 hours per week from 7 December 2026 to 8 March 2027.
> 2. Why Git and Outreachy?
> To me, Git is the reason behind successful software development. I usually use Git
> mainly as a tool for tracking changes or versions, working with branches, and
> collaborating with other developers.
Atos is a trading name used by the Atos group. The trading entity is registered in England and Wales: Atos IT Services UK Limited (registered number 01245534). The registered office is located at: Second Floor, MidCity Place, 71 High Holborn, London, WC1V 6EA. The VAT No. is: GB232327983. This e-mail and the documents attached are confidential and intended solely for the addressee and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use, or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended, or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.
Previous: Fien DoraNext: Junio C Hamano
Message 2 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.