From: Nicolas Bock <nicolasbock@gmail.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: merge broken mail threads
Date: Wed, 23 Jan 2019 14:19:02 -0700 [thread overview]
Message-ID: <87va2fgji1.fsf@gmail.com> (raw)
In-Reply-To: <87h8dz5np2.fsf@fifthhorseman.net>
On Wed, Jan 23 2019, Daniel Kahn Gillmor wrote:
> On Wed 2019-01-23 08:29:05 -0700, Nicolas Bock wrote:
>
>> Sometimes during a lengthy discussion someone inadvertently
>> breaks the email thread because their mail client doesn't get
>> it. Is there a way to merge the two fragmented threads again
>> with notmuch?
>
> there's a manual way to do it as a janky workaround:
>
> * create a bogus e-mail message that References: a message-id
> from each
> split faction.
>
> * inject that message into your notmuch message store
>
> * delete that message
Nice trick :) Would this also work if I modified the reference of
the first email that breaks the thread to point to the email it is
quoting? I would have to get notmuch to re-read that email though
to update the database. But this approach would not involve first
creating a fake message and then deleting it again :)
> See also the thread on this maiing list with Subject "thread merge/split
> proposal" from back in 2016, starting at
> id:87mvp9uwi4.fsf@alice.fifthhorseman.net though i don't think any of
> that has been implemented.
>
> --dkg
next prev parent reply other threads:[~2019-01-23 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 15:29 merge broken mail threads Nicolas Bock
2019-01-23 16:43 ` Daniel Kahn Gillmor
2019-01-23 21:19 ` Nicolas Bock [this message]
2019-01-24 11:05 ` David Bremner
2019-01-24 16:31 ` Daniel Kahn Gillmor
2019-01-23 21:48 ` Tomi Ollila
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=87va2fgji1.fsf@gmail.com \
--to=nicolasbock@gmail.com \
--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).