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

Re: [PATCH v2] send-email: make it easy to discern the messages for each patch

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 5, 2024, 17:13 UTC
Message-ID
<xmqqplv3vijx.fsf@gitster.g>
In-Reply-To
<fa91b134e6cb18578d9c499f584ae3c5@manjaro.org>
Dragan Simic <dsimic@manjaro.org> writes:
> However, making the vertical whitespace a separator also follows
> the Git's general approach of not wasting the vertical screen
> space whenever possible, so taking the separator route is actually
> better, if you agree.
Of course.

If the topic came from a contributor with a longer track record and used terminator semantics, I would have insisted to consider separator semantics a lot more strongly. With only two commits in this history of any tagged releases, you are getting a bit more lenient treatment ;-)

Previous: Dragan SimicNext: Dragan Simic
Message 6 of 9 in “send-email: make it easy to discern the messages for each patch”
  1. send-email: make it easy to discern the messages for each patchDragan Simic, Apr 4, 2024
  2. Junio C HamanoApr 4, 2024
  3. Dragan SimicApr 4, 2024
  4. Junio C HamanoApr 5, 2024
  5. Dragan SimicApr 5, 2024
  6. Junio C HamanoApr 5, 2024
  7. Dragan SimicApr 5, 2024
  8. Kristoffer HaugsbakkApr 5, 2024
  9. Dragan SimicApr 5, 2024

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.