From: Brian May <brian@linuxpenguins.xyz>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
David Bremner <david@tethera.net>,
notmuch@notmuchmail.org
Subject: Re: Weird tagging issue
Date: Mon, 30 Mar 2020 10:55:40 +1100 [thread overview]
Message-ID: <87zhbyu35v.fsf@silverfish.pri> (raw)
In-Reply-To: <87ftdq6971.fsf@fifthhorseman.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>> "1584434229.8921_0.wspdigital:2,S" -> { "pr-wspdigital/bupaoshc/88@bitbucket.org" }
>> "1584434231.8924_0.wspdigital:2,S" -> { "pr-wspdigital/bupaoshc/88@bitbucket.org" }
>> "1584434232.8927_0.wspdigital:2,S" -> { "pr-wspdigital/bupaoshc/88@bitbucket.org" }
>> "1584434234.8930_0.wspdigital:2,S" -> { "pr-wspdigital/bupaoshc/88@bitbucket.org" }
>
> The surprising thing about this output is that there appear to be 4
> copies of message that References: itself!
>
> And, many many other messages also reference that message too.
>
> Would you be willing to send me the full headers from one of the above 4
> files so i can verify that this is correct?
I suspect you only need the Message-ID and the References headers,
right? If not, can send more:
Message-ID: <pr-wspdigital/bupaoshc/88@bitbucket.org>
References: <pr-wspdigital/bupaoshc/88@bitbucket.org>
This applies to all 4 of those messages. Yes, they all look like they
have the same Message-ID
Also I am not seeing any duplicate headers or anything like that.
--
Brian May <brian@linuxpenguins.xyz>
https://linuxpenguins.xyz/brian/
next prev parent reply other threads:[~2020-03-29 23:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 4:27 Weird tagging issue Brian May
2020-03-20 0:06 ` Brian May
2020-03-21 1:03 ` Daniel Kahn Gillmor
2020-03-22 21:22 ` Brian May
2020-03-23 1:12 ` David Bremner
2020-03-23 2:58 ` Daniel Kahn Gillmor
2020-03-29 21:03 ` Brian May
2020-03-29 23:19 ` Daniel Kahn Gillmor
2020-03-29 23:55 ` Brian May [this message]
2020-03-30 0:53 ` Carl Worth
2020-03-30 5:22 ` Daniel Kahn Gillmor
2020-03-30 21:16 ` Brian May
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=87zhbyu35v.fsf@silverfish.pri \
--to=brian@linuxpenguins.xyz \
--cc=david@tethera.net \
--cc=dkg@fifthhorseman.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).