--- /dev/null
+Return-Path: <dkg@fifthhorseman.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 6CFD440DDE7\r
+ for <notmuch@notmuchmail.org>; Fri, 12 Nov 2010 18:20:52 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.899\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5\r
+ tests=[BAYES_00=-1.9, UNPARSEABLE_RELAY=0.001] autolearn=ham\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id ubqu1BCHQSQJ for <notmuch@notmuchmail.org>;\r
+ Fri, 12 Nov 2010 18:20:42 -0800 (PST)\r
+Received: from rodolpho.mayfirst.org (mail.freitas.net [209.234.253.107])\r
+ (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 4F99540DDC1\r
+ for <notmuch@notmuchmail.org>; Fri, 12 Nov 2010 18:20:42 -0800 (PST)\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by rodolpho.mayfirst.org (Postfix) with ESMTP id A51783CD51\r
+ for <notmuch@notmuchmail.org>; Fri, 12 Nov 2010 21:20:39 -0500 (EST)\r
+X-Virus-Scanned: Debian amavisd-new at rodolpho.mayfirst.org\r
+Received: from rodolpho.mayfirst.org ([127.0.0.1])\r
+ by localhost (rodolpho.mayfirst.org [127.0.0.1]) (amavisd-new,\r
+ port 10024) with ESMTP id 5yW7TdF1Eh1a for <notmuch@notmuchmail.org>;\r
+ Fri, 12 Nov 2010 21:20:39 -0500 (EST)\r
+Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender:\r
+ smtpauth@rodolpho.mayfirst.org) with ESMTPSA id 5DCE93CD4B\r
+Message-ID: <4CDDF5F3.9040800@fifthhorseman.net>\r
+Date: Fri, 12 Nov 2010 21:20:35 -0500\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;\r
+ rv:1.9.2.9) Gecko/20100918 Icedove/3.1.4\r
+MIME-Version: 1.0\r
+To: notmuch <notmuch@notmuchmail.org>\r
+Subject: splittng threads [was: Re: Combining threads]\r
+References: <AANLkTimDjk_-Xjpf6uovGXgyG_3j-ySLWQR+0UvdVjjT@mail.gmail.com>\r
+ <87mxpe81t9.fsf@yoom.home.cworth.org>\r
+In-Reply-To: <87mxpe81t9.fsf@yoom.home.cworth.org>\r
+X-Enigmail-Version: 1.1.2\r
+OpenPGP: id=D21739E9\r
+Content-Type: multipart/signed; micalg=pgp-sha512;\r
+ protocol="application/pgp-signature";\r
+ boundary="------------enigC52BB2FCC997C6F3F93D148E"\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+Reply-To: notmuch <notmuch@notmuchmail.org>\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 13 Nov 2010 02:20:52 -0000\r
+\r
+This is an OpenPGP/MIME signed message (RFC 2440 and 3156)\r
+--------------enigC52BB2FCC997C6F3F93D148E\r
+Content-Type: text/plain; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+(hi list -- i'm new here; don't be afraid to explain things to me that\r
+seem obvious to you, or correct my vocabulary if i'm using it wrong)\r
+\r
+On 11/12/2010 08:11 PM, Carl Worth wrote:\r
+> But I suppose it's as simple a matter of creating a new "top-level\r
+> message" term in the database. The split operation would set this\r
+> term. The explicit join operation would clear it, and the implicit join=\r
+\r
+> operation would have to be made to respect it by avoiding merging any\r
+> top-level messages as a child of some other message. I haven't thought\r
+> through exactly how that would work in the implementation, but hopefull=\r
+y\r
+> it wouldn't be too hard.\r
+\r
+my current understanding is that a not-uncommon use case is to have two\r
+separate notmuch instances, synchronized by syncing maildirs and\r
+tagsets. Would such a thread-split be syncable between two notmuch\r
+instances?\r
+\r
+ --dkg\r
+\r
+\r
+--------------enigC52BB2FCC997C6F3F93D148E\r
+Content-Type: application/pgp-signature; name="signature.asc"\r
+Content-Description: OpenPGP digital signature\r
+Content-Disposition: attachment; filename="signature.asc"\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.10 (GNU/Linux)\r
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/\r
+\r
+iQIcBAEBCgAGBQJM3fXzAAoJEMzS7ZTSFznp4asP+wbTrdsom7/G+lpv8uSsgf0+\r
+4qQlI2g/dx3EUHYvZbXHjlhTO43y5sNOkR2sxda4z3Oo5CtnfZyfPXdXa011hBpJ\r
+/39i5uCxtoMG1q4bV8Hl0sNwWWrzvUcQ1ZZRevTWavsmChD2FjgALVjXmmY+Tkfr\r
+TiUleM9BcRN5ckQPCxvS3ecx30QT8BlF7IzDFDd3uYfmQGnDWteeircM6GktDFB2\r
+2P59oyENSbgVIVSVLXFm0oxvhc9hdjFBEFW65s4JI/cdk4OLlXoZZVC6nz3VCdyW\r
+JZ4zP1+qyTfaJot5fPGTBWzVOJXuwdAJpcRaLUc2cMfhs3/n4PLB87Io1qNuBw8k\r
+rodiFHRN94Ngfp0STsFw4k4N3Sm4jxoZFyMjuBQVAUu1I/dy+IB5BvM3kpSiFW+M\r
+jDJE45QaPuO2eHB9C0Z9xXvHHuzKK0EJXTnShFJqqN8R060ME/W6TO2/emRNWRG7\r
+q7OQBnJ/r+rrmajRcjnl+cbRO7TJzhpwTBHRN9PeDUDF4rse628WI1MTdiQ1irMJ\r
+jbbrnAo8yPX6YcMWdi63m+0HJtm6f9Z5pfwVqzjlXs+W7h7lq/EsEOSaILQnTJdF\r
+DzfS1uHwvResMYuDvPyGnrZPV1jP2bQ27/7WMJsnyZ9fQuEEF6OJGcMgpP41GbZt\r
+NvZRrUWT+JZOsRe3PCQn\r
+=5ZkO\r
+-----END PGP SIGNATURE-----\r
+\r
+--------------enigC52BB2FCC997C6F3F93D148E--\r
projects / notmuch-archives.git / blobdiff