Re: Breaking a really long thread

diff --git a/44/dcdeeca8bcdbcff1506648fc0e52df91f5e271 b/44/dcdeeca8bcdbcff1506648fc0e52df91f5e271
new file mode 100644 (file)
index 0000000..a52095d
--- /dev/null
+++ b/44/dcdeeca8bcdbcff1506648fc0e52df91f5e271
@@ -0,0 +1,73 @@
+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 6EC516DE02DD\r
+ for <notmuch@notmuchmail.org>; Sat,  9 Apr 2016 11:32:58 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.476\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.476 tagged_above=-999 required=5 tests=[AWL=-0.627,\r
+  DATE_IN_PAST_06_12=1.103] 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 av1qcVqfF91j for <notmuch@notmuchmail.org>;\r
+ Sat,  9 Apr 2016 11:32:50 -0700 (PDT)\r
+Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])\r
+ by arlo.cworth.org (Postfix) with ESMTP id B7CC56DE02BF\r
+ for <notmuch@notmuchmail.org>; Sat,  9 Apr 2016 11:32:50 -0700 (PDT)\r
+Received: from fifthhorseman.net (ool-6c3a0662.static.optonline.net\r
+ [108.58.6.98])\r
+ by che.mayfirst.org (Postfix) with ESMTPSA id 3DADDFED8;\r
+ Sat,  9 Apr 2016 14:32:39 -0400 (EDT)\r
+Received: by fifthhorseman.net (Postfix, from userid 1000)\r
+ id D45AE20B12; Sat,  9 Apr 2016 08:20:47 -0300 (BRT)\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+To: David Mazieres expires 2016-07-03 PDT\r
+ <mazieres-297ctmng4fhr6h6ad8yffa64yi@temporary-address.scs.stanford.edu>,\r
+ Mark Walters <markwalters1009@gmail.com>, Eric <eric@deptj.eu>,\r
+ notmuch@notmuchmail.org\r
+Subject: Re: Breaking a really long thread\r
+In-Reply-To: <87wpoc7hf8.fsf@ta.scs.stanford.edu>\r
+References: <c10e501c2baee471cbeeb42aad89a1e966407234-NM@bruno.deptj.eu>\r
+ <87k2kd8r6d.fsf@qmul.ac.uk> <87wpoc7hf8.fsf@ta.scs.stanford.edu>\r
+User-Agent: Notmuch/0.21+124~gbf604e9 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 09 Apr 2016 07:20:47 -0400\r
+Message-ID: <8760vrm3jk.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: Sat, 09 Apr 2016 18:32:58 -0000\r
+\r
+On Tue 2016-04-05 01:28:43 -0400, David Mazieres wrote:\r
+> Arguably, I would say either both the In-Reply-To and the References\r
+> header should be hidden or neither.  Otherwise, what was happening is\r
+> that I was deleting the In-Reply-To header as it was the only one I saw,\r
+> and figuring that maybe References was adjusted after the fact based on\r
+> In-Reply-To.  After all, the message buffer doesn't keep track of the\r
+> parent message.\r
+>\r
+> Unless there's a reason that someone would want to alter In-Reply-To\r
+> without altering References, it doesn't make sense to show one without\r
+> the other.\r
+\r
+I think i agree with David here, but the fact is that\r
+message-hidden-headers is derived directly from emacs (in message.el),\r
+and isn't part of notmuch-emacs at all.\r
+\r
+Are these changes worth addressing upstream?\r
+\r
+    --dkg\r