Re: thread merge/split proposal

diff --git a/a2/0758063525b25163f2e8c87a3cf2b2ef676259 b/a2/0758063525b25163f2e8c87a3cf2b2ef676259
new file mode 100644 (file)
index 0000000..d737f57
--- /dev/null
+++ b/a2/0758063525b25163f2e8c87a3cf2b2ef676259
@@ -0,0 +1,96 @@
+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 arlo.cworth.org (Postfix) with ESMTP id F0C2A6DE012F\r
+ for <notmuch@notmuchmail.org>; Mon, 11 Apr 2016 18:30:04 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.019\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.019 tagged_above=-999 required=5\r
+ tests=[AWL=-0.019] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id aIuQcet-_0x3 for <notmuch@notmuchmail.org>;\r
+ Mon, 11 Apr 2016 18:29:56 -0700 (PDT)\r
+Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 7CFB06DE0159\r
+ for <notmuch@notmuchmail.org>; Mon, 11 Apr 2016 18:29:56 -0700 (PDT)\r
+Received: from fifthhorseman.net (unknown [38.109.115.130])\r
+ by che.mayfirst.org (Postfix) with ESMTPSA id 4CBEDF991;\r
+ Mon, 11 Apr 2016 21:29:55 -0400 (EDT)\r
+Received: by fifthhorseman.net (Postfix, from userid 1000)\r
+ id F22D820072; Mon, 11 Apr 2016 21:29:54 -0400 (EDT)\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+To: David Bremner <david@tethera.net>, Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: Re: thread merge/split proposal\r
+In-Reply-To: <8737qr7ig6.fsf@zancas.localnet>\r
+References: <87mvp9uwi4.fsf@alice.fifthhorseman.net>\r
+ <87k2kdutao.fsf@alice.fifthhorseman.net> <878u0l8uyv.fsf@zancas.localnet>\r
+ <87egabu5ta.fsf@alice.fifthhorseman.net> <8737qr7ig6.fsf@zancas.localnet>\r
+User-Agent: Notmuch/0.21+124~gbf604e9 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Mon, 11 Apr 2016 21:29:54 -0400\r
+Message-ID: <87d1pvsjfx.fsf@alice.fifthhorseman.net>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 12 Apr 2016 01:30:05 -0000\r
+\r
+On Mon 2016-04-11 20:56:57 -0400, David Bremner wrote:\r
+> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:\r
+>\r
+>> I'm not sure what you mean by "signed" here (cryptographically signed?\r
+>> a term named "signed"?  the idea that the term could be either positive\r
+>> or negative?), but i think your proposal is that we could have a\r
+>> "reference" term with a value of "+foo@example.com" or\r
+>> "-foo@example.com", instead of having a "join" term with value\r
+>> "foo@example.com" and a "split" term with value "foo@example.com"\r
+>\r
+> I was thinking mostly in terms of the UI. I think\r
+>\r
+> %  notmuch reference +id1 -id2 $QUERY\r
+>         \r
+> goes well with the tag interface.\r
+\r
+I see, yeah, that makes sense.\r
+\r
+That still doesn't cover the "notmuch unjoin" semantics i'd sketched out\r
+earlier, though.  that might need to be a different use case.\r
+\r
+The semantics would be something like:\r
+\r
+  break the selected threads into threads based solely on their\r
+  References headers (including any manual reference terms) using\r
+  connected component analysis, restoring the threading to what would be\r
+  produced on a clean import.\r
+\r
+maybe "unjoin" is the wrong verb, but i'm open to suggestions.\r
+\r
+> I'm a bit worried about UI proliferation with notmuch-join,\r
+> notmuch-unjoin now and maybe notmuch-split, notmuch-unsplit later. I'd\r
+> be fine with a more generic command with parts perhaps unimplimented.\r
+\r
+i see, that makes sense.\r
+\r
+> Making things generic in the right way will be less work in the long\r
+> run, I think.  For example, if we had thought about more general terms\r
+> attached to a message in the last revision of dump/restore, we'd be done\r
+> now. \r
+\r
+right -- we don't even have any version information in the notmuch dump\r
+file.  what's the right way to approach this?\r
+\r
+       --dkg\r