Github messages for mblaze
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Unresolved entries in sequence with mthread
Date: Sat, 20 Nov 2021 11:45:16 +0100	[thread overview]
Message-ID: <20211120104516.rNswnpSZ37QBFAhBlIH8b3366_HYqm-twdWZb_vKuUw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-218@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

New comment by Duncaen on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/218#issuecomment-974629671

Comment:
This happens if there is a mail with `In-Reply-To` header to a message id that is not part of the mails passed to `mthread`, so instead of silently ignoring this, it prints the message id and uses that as parent.
Sequences that are not threaded don't look at the `In-Reply-To` header so they don't add those missing message ids.

This could have been either someone mailing the person replying to the non-existing message-id directly instead of the list who then replies back to the mailing list.
Another possibility is that the message ends up in spam filter/folder and is not part of the sequence passed to `mthread`.
Some automatic mails, like from github threads will just put a non-existing message id into `In-Reply-To` to group mails about issue comments into a thread which are not actually threaded.

  parent reply	other threads:[~2021-11-20 10:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-20  2:45 [ISSUE] " fagg
2021-11-20 10:38 ` Duncaen
2021-11-20 10:39 ` Duncaen
2021-11-20 10:45 ` Duncaen [this message]
2021-11-20 10:45 ` Duncaen
2021-11-20 18:02 ` fagg
2021-11-20 18:02 ` [ISSUE] [CLOSED] " fagg

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=20211120104516.rNswnpSZ37QBFAhBlIH8b3366_HYqm-twdWZb_vKuUw@z \
    --to=duncaen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).