{"thread":{"id":"48309","subject":"git send-mail sends with duplicate In-Reply-To/References header fields","startedAt":"2018-04-17T08:42:16Z","lastAt":"2018-04-17T08:42:16Z","messageCount":1,"participants":["Stefan Agner"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"344867","messageId":"997160314bbafb3088a401f1c09ccb08@agner.ch","threadId":"48309","inReplyTo":null,"subject":"git send-mail sends with duplicate In-Reply-To/References header fields","fromName":"Stefan Agner","fromEmail":"stefan@agner.ch","sentAt":"2018-04-17T08:42:06Z","receivedAt":"2018-04-17T08:42:16Z","isPatch":false,"sender":{"key":"stefan@agner.ch","avatar":"https://avatars.githubusercontent.com/u/34061?v=4"},"body":"Hi,\n\nUsing git format-patch --thread + send-mail leads to\nIn-Reply-To/References headers added twice (with the very same value).\nThis is not allowed according to RFC 5322 Section 3.6:\nhttps://tools.ietf.org/html/rfc5322#section-3.6\n\nIdeally probably git-format-patch should be smart about whether\nIn-Reply-To/References are already present...\n\nI noticed this after looking through emails catched by my spam filter\nmore carefully. It seems that this particular violation is penalized\nquite harshly, leading to those emails landing in my spam folder. It\nseems that there are multiple kernel developers which use the above work\nflow and hence send emails not adhering to spec...\n\n--\nStefan\n"}]}