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

git send-mail sends with duplicate In-Reply-To/References header fields

From
Stefan Agner <stefan@agner.ch>
Date
Apr 17, 2018, 08:42 UTC
Message-ID
<997160314bbafb3088a401f1c09ccb08@agner.ch>
Hi,

Using git format-patch --thread + send-mail leads to In-Reply-To/References headers added twice (with the very same value). This is not allowed according to RFC 5322 Section 3.6: https://tools.ietf.org/html/rfc5322#section-3.6

Ideally probably git-format-patch should be smart about whether In-Reply-To/References are already present...

I noticed this after looking through emails catched by my spam filter more carefully. It seems that this particular violation is penalized quite harshly, leading to those emails landing in my spam folder. It seems that there are multiple kernel developers which use the above work flow and hence send emails not adhering to spec...

-- Stefan

Message 1 of 1 in “git send-mail sends with duplicate In-Reply-To/References header fields”
  1. Stefan AgnerApr 17, 2018

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.