Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: Gnus wrong message threading
Date: Sun, 20 Sep 2020 14:17:39 +0200	[thread overview]
Message-ID: <87y2l4myl8.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87pn6g1y6w.fsf@fedora.osfans.org>

Kevin writes:

> I view with trn-style threads with %B mentioned in my previous mail,
> no [] and <> characters.

So you want a feature you have explicitly turned off?

> Found gnus-summary-reparent-thread and gnus-summary-reparent-children
> equivalent to link-threads. :-)
> But still no break-thread equivalent commands.

And the bug you found in threading is... what again?

>> What is your point?
>
> I mean they were old MUAs back in *2012* that don't generate the two
> headers.

Uhm, the examples I showed of Gmail and GMX generating In-Reply-To and
References were from 2012 as well.

Those headers are much older than 2012, they are in RFC 822¹ from 1982
and in the previous RFC 733² from 1977; what is the point you're trying
to make?


  Best regards,

    Adam

¹ https://tools.ietf.org/html/rfc822
² https://tools.ietf.org/html/rfc733

-- 
 "we have stairs in our house."                             Adam Sjøgren
                                                       asjo@koldfront.dk



  reply	other threads:[~2020-09-20 12:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-19  2:15 Kevin Shell
2020-09-19 11:23 ` Adam Sjøgren
2020-09-19 13:56   ` Kevin Shell
2020-09-19 14:08     ` Adam Sjøgren
2020-09-20  2:33       ` Kevin Shell
2020-09-20  9:51         ` Adam Sjøgren
2020-09-20 10:33           ` Kevin Shell
2020-09-20 10:58             ` Adam Sjøgren
2020-09-20 11:31               ` Kevin Shell
2020-09-20 12:17                 ` Adam Sjøgren [this message]
2020-09-19 14:14     ` 황병희

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

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

  git send-email \
    --in-reply-to=87y2l4myl8.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).