From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: notmuch <notmuch@notmuchmail.org>
Subject: splittng threads [was: Re: Combining threads]
Date: Fri, 12 Nov 2010 21:20:35 -0500 [thread overview]
Message-ID: <4CDDF5F3.9040800@fifthhorseman.net> (raw)
In-Reply-To: <87mxpe81t9.fsf@yoom.home.cworth.org>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
(hi list -- i'm new here; don't be afraid to explain things to me that
seem obvious to you, or correct my vocabulary if i'm using it wrong)
On 11/12/2010 08:11 PM, Carl Worth wrote:
> But I suppose it's as simple a matter of creating a new "top-level
> message" term in the database. The split operation would set this
> term. The explicit join operation would clear it, and the implicit join
> operation would have to be made to respect it by avoiding merging any
> top-level messages as a child of some other message. I haven't thought
> through exactly how that would work in the implementation, but hopefully
> it wouldn't be too hard.
my current understanding is that a not-uncommon use case is to have two
separate notmuch instances, synchronized by syncing maildirs and
tagsets. Would such a thread-split be syncable between two notmuch
instances?
--dkg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2010-11-13 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 16:57 Combining threads Scott Henson
2010-11-13 1:11 ` Carl Worth
2010-11-13 2:20 ` Daniel Kahn Gillmor [this message]
2010-11-14 22:24 ` splittng threads [was: Re: Combining threads] Michal Sojka
2010-11-14 23:58 ` David Bremner
2010-11-14 22:21 ` Web archive (was: Combining threads) Michal Sojka
2010-11-14 23:32 ` Jameson Rollins
2012-09-25 16:08 ` On splitting threads - Was: Re: Combining threads Olivier Berger
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=4CDDF5F3.9040800@fifthhorseman.net \
--to=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).