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

Re: [PATCH] send-email: Refuse to send cover-letter template subject

From
Markus Heidelberg <markus.heidelberg@web.de>
Date
Jun 9, 2009, 19:32 UTC
Message-ID
<200906092132.10256.markus.heidelberg@web.de>
In-Reply-To
<7v4oupmdv5.fsf@alter.siamese.dyndns.org>
Junio C Hamano, 09.06.2009:
Show 7 quoted lines
> Markus Heidelberg <markus.heidelberg@web.de> writes:
> >
> > My mail "[PATCH 0/6] fixes for git-send-email" had an empty blurb
> > section because it didn't need any additional description.
> > I wouldn't want git to refuse sending it.
> 
> I actually wouldn't have wanted to see that [0/6] with empty description.

I thought the diffstat is a nice overview as well. So there is at least some value in a blurb-less cover letter. But I guess they are debatable.

> If the list of 6 patch titles give clear enough description of the theme
> of the whole series, you would not need [0/6] to set the stage,

I prefer --thread --no-chain-reply-to for more than 2 patches, so it seems I sometimes only abuse the 0/X as a common anchor for 1..X/X. I'd find it strange to use 1/X for that.

> and that is the best kind of series.
Hmm, so then you prefer no 0/X at all.
Previous: Junio C Hamano
Message 8 of 8 in “send-email: Refuse to send cover-letter template subject”
  1. send-email: Refuse to send cover-letter template subjectThomas Rast, Jun 8, 2009
  2. Junio C HamanoJun 8, 2009
  3. Thomas RastJun 9, 2009
  4. Thomas RastJun 12, 2009
  5. Junio C HamanoJun 12, 2009
  6. Markus HeidelbergJun 9, 2009
  7. Junio C HamanoJun 9, 2009
  8. Markus HeidelbergJun 9, 2009

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.