user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@yhbt.net>
Cc: meta@public-inbox.org
Subject: Re: How to force stricter threading
Date: Thu, 19 Mar 2020 14:45:52 -0400	[thread overview]
Message-ID: <20200319184552.4zxqket35fij64ua@chatter.i7.local> (raw)
In-Reply-To: <20200319075820.GA13992@dcvr>

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-summary@kernel.org/raw
> > 
> > has the following header:
> > 
> > References: <20200217101741.3758-1-geert+renesas@glider.be>,
> >  <20200218112414.5591-1-geert+renesas@glider.be>,
> >  <20200218112449.5723-1-geert+renesas@glider.be>,
> >  <20200219153929.11073-1-geert+renesas@glider.be>,
> >  <20200218132217.21454-1-geert+renesas@glider.be>,
> >  <20200217103251.5205-1-geert+renesas@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

      reply	other threads:[~2020-03-19 18:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09 13:15 How to force stricter threading Konstantin Ryabitsev
2020-03-11 10:20 ` Eric Wong
2020-03-19  7:22 ` Eric Wong
2020-03-19  7:58   ` Eric Wong
2020-03-19 18:45     ` Konstantin Ryabitsev [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200319184552.4zxqket35fij64ua@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=e@yhbt.net \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).