unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH] test: add known broken test for thread fusion bug
Date: Fri, 31 Dec 2021 08:51:09 -0400	[thread overview]
Message-ID: <87r19tey4i.fsf@tethera.net> (raw)
In-Reply-To: <20211226161716.2079457-1-david@tethera.net>

David Bremner <david@tethera.net> writes:

> This particular bug is apparently caused by the malformed (according
> to RFC5822 section 3.6.4) In-reply-to field of
> id:5422.1299798393@alphaville.usa.hp.com.

I'm having second thoughts about this test. I'm not sure notmuch can do
better than treat all of the things that look like message-ids in
In-reply-to as references.

RFC 5322 (which I called 5822 above) talks about obsolete syntax, and in
particular 4.5.4 discusses obsolete In-Reply-To and References
syntax. I _think_ (but am not 100% sure), that even under that generous
syntax, just grabbing the things that look like message-ids is the best
thing to do.

d


      reply	other threads:[~2021-12-31 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-26 16:17 [PATCH] test: add known broken test for thread fusion bug David Bremner
2021-12-31 12:51 ` David Bremner [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: https://notmuchmail.org/

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

  git send-email \
    --in-reply-to=87r19tey4i.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).