From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: thread merge/split proposal
Date: Sun, 07 Aug 2016 08:50:54 +0900 [thread overview]
Message-ID: <878tw98nj5.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <87d1pvsjfx.fsf@alice.fifthhorseman.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
> That still doesn't cover the "notmuch unjoin" semantics i'd sketched out
> earlier, though. that might need to be a different use case.
>
> The semantics would be something like:
>
> break the selected threads into threads based solely on their
> References headers (including any manual reference terms) using
> connected component analysis, restoring the threading to what would be
> produced on a clean import.
One thing I haven't understood is if the problem this is working around
is unavoidable due to the order messages arrive (or some other factor)
or if this is just a workaround for bugs in the threading algorithm. I'm
guessing the former, but can you explain why the problem is intractable
enough that the right answer is to reindex a thread (btw, that might be
a UI, to use the reindex command introduced in your indexed plaintex
patches).
d
prev parent reply other threads:[~2016-08-06 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 17:14 thread merge/split proposal Daniel Kahn Gillmor
2016-04-04 18:23 ` Daniel Kahn Gillmor
2016-04-10 13:16 ` David Bremner
2016-04-11 22:41 ` Daniel Kahn Gillmor
2016-04-12 0:56 ` David Bremner
2016-04-12 1:29 ` Daniel Kahn Gillmor
2016-08-06 23:50 ` 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=878tw98nj5.fsf@maritornes.cs.unb.ca \
--to=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).