Re: Breaking a really long thread

diff --git a/11/0076efc6a1d959b6e8d3438a2a8e3e71726092 b/11/0076efc6a1d959b6e8d3438a2a8e3e71726092
new file mode 100644 (file)
index 0000000..5c152fa
--- /dev/null
+++ b/11/0076efc6a1d959b6e8d3438a2a8e3e71726092
@@ -0,0 +1,79 @@
+Return-Path: <david@tethera.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 906F06DE02A7\r
+ for <notmuch@notmuchmail.org>; Sat,  2 Apr 2016 05:41:21 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.021\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.021 tagged_above=-999 required=5\r
+ tests=[AWL=-0.010, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01]\r
+ 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 8ainMvz3b9bJ for <notmuch@notmuchmail.org>;\r
+ Sat,  2 Apr 2016 05:41:13 -0700 (PDT)\r
+Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id CEF6F6DE0281\r
+ for <notmuch@notmuchmail.org>; Sat,  2 Apr 2016 05:41:12 -0700 (PDT)\r
+Received: from remotemail by fethera.tethera.net with local (Exim 4.84)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1amKs4-00023V-87; Sat, 02 Apr 2016 08:41:44 -0400\r
+Received: (nullmailer pid 2988 invoked by uid 1000);\r
+ Sat, 02 Apr 2016 12:41:08 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: David Mazieres expires 2016-06-30 PDT\r
+ <mazieres-fmzyazpz6acxdkzys7pkrhp8ve@temporary-address.scs.stanford.edu>,\r
+ notmuch@notmuchmail.org\r
+Subject: Re: Breaking a really long thread\r
+In-Reply-To: <87twjkopb8.fsf@ta.scs.stanford.edu>\r
+References: <1459015043-8460-1-git-send-email-david@tethera.net>\r
+ <87twjkopb8.fsf@ta.scs.stanford.edu>\r
+User-Agent: Notmuch/0.21+74~g6c60fb1 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 02 Apr 2016 09:41:08 -0300\r
+Message-ID: <87a8lci3ob.fsf@zancas.localnet>\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: Sat, 02 Apr 2016 12:41:21 -0000\r
+\r
+David Mazieres <dm-list-email-notmuch@scs.stanford.edu> writes:\r
+\r
+\r
+> Is there any way to break an existing thread (so as to start over with a\r
+> smaller thread), or otherwise to tweak the threading rules so that a\r
+> particular References header gets ignored.\r
+\r
+Currently there is no way to do this, as threads are "stateless"\r
+i.e. created on the fly by _notmuch_create_thread based only on\r
+immutable mail data.  We'd have to be willing to dump/restore any\r
+threading hints we added to the database, but we're already headed down\r
+that path with the libconfig stuff anyway.  Something we _almost_ have\r
+the infrastructure in place for would be to blacklist a particular\r
+reference (e.g. by regex) by storing the blacklist as database\r
+metadata. That would solve your particular problem, although I'm not\r
+sure it it's general enough. Keeping global state for all thread\r
+breaking sounds a bit clunky.\r
+\r
+> It's annoyingly slow to open\r
+> a thread with 10,000 messages just to read one SMS.  I'm almost tempted\r
+> to mangle the messages on delivery and remove the References header\r
+> before notmuch sees them, but it would be nice to have a cleaner\r
+> solution, as there are other situations in which one might want to\r
+> "reset" a really long thread.\r
+\r
+Like this thread ;).\r