On Thu, Mar 19, 2020 at 07:58:20AM +0000, Eric Wong wrote: > > So the "Patchwork summary for: linux-renesas-soc" message: > > > > https://lore.kernel.org/linux-renesas-soc/158229483332.12219.5639020605006542672.git-patchwork-summ...@kernel.org/raw > > > > has the following header: > > > > References: <20200217101741.3758-1-geert+rene...@glider.be>, > > <20200218112414.5591-1-geert+rene...@glider.be>, > > <20200218112449.5723-1-geert+rene...@glider.be>, > > <20200219153929.11073-1-geert+rene...@glider.be>, > > <20200218132217.21454-1-geert+rene...@glider.be>, > > <20200217103251.5205-1-geert+rene...@glider.be> > > > > Which seems to have tied a bunch of unrelated threads together > > as one, similar to how a merge commit works in git but is > > unexpected and rare for mail threads.
Thanks for tracking that down. > > But the thread rendering could be improved. What mutt does > > seems alright, but doesn't convey the "merge" scenario > > (I think) your bot was going for... > > Fwiw, RFC 5322 sec 3.6.4 states: > > Therefore, trying to form a "References:" field for a reply that > has multiple parents is discouraged; how to do so is not defined > in this document. > > So there's also that... I'll plan to stop adding these to the References: header and just give lore.kernel.org/r/<msgid> links. I don't think anyone would care and it will avoid this problem. Thanks again, -K
