From: David Bremner <bremner@unb.ca>
To: Michal Sojka <sojkam1@fel.cvut.cz>,
	Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	notmuch <notmuch@notmuchmail.org>
Subject: Re: splittng threads [was: Re: Combining threads]
In-Reply-To: <87bp5rr1bq.fsf@steelpick.2x.cz>
References: <AANLkTimDjk_-Xjpf6uovGXgyG_3j-ySLWQR+0UvdVjjT@mail.gmail.com>
	<87mxpe81t9.fsf@yoom.home.cworth.org>
	<4CDDF5F3.9040800@fifthhorseman.net>
	<87bp5rr1bq.fsf@steelpick.2x.cz>
User-Agent: Notmuch/0.4 (http://notmuchmail.org) Emacs/23.2.1
	(x86_64-pc-linux-gnu)
Date: Sun, 14 Nov 2010 19:58:40 -0400
Message-ID: <87fwv3bgpb.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Precedence: list

On Sun, 14 Nov 2010 23:24:09 +0100, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
> On Sat, 13 Nov 2010, Daniel Kahn Gillmor wrote:
> > 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?
> 
> It won't be syncable without a special support somewhere in notmuch.
> 

To elaborate, threads are currently reconstructed in every instance
rather than being syncable. This is mainly because the thread-ids are
generated sequentially. Since messages could arrive in different
instances at different times, assigning the "right" thread-id is a bit
non-trivial.