RE: Reply all - issue

diff --git a/c4/6ad5f339f20fb60d52babff4ae8e8a57c42a78 b/c4/6ad5f339f20fb60d52babff4ae8e8a57c42a78
new file mode 100644 (file)
index 0000000..aade1e1
--- /dev/null
+++ b/c4/6ad5f339f20fb60d52babff4ae8e8a57c42a78
@@ -0,0 +1,113 @@
+Return-Path: <jrollins@finestructure.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 7C549431FBC\r
+       for <notmuch@notmuchmail.org>; Mon, 11 Feb 2013 23:08:07 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=unavailable\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 VLQhBVMnYWvn for <notmuch@notmuchmail.org>;\r
+       Mon, 11 Feb 2013 23:08:07 -0800 (PST)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+       [131.215.239.19])\r
+       by olra.theworths.org (Postfix) with ESMTP id 564DC431FAF\r
+       for <notmuch@notmuchmail.org>; Mon, 11 Feb 2013 23:08:07 -0800 (PST)\r
+Received: from earth-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+       by earth-doxen-postvirus (Postfix) with ESMTP id C8D9866E00CF;\r
+       Mon, 11 Feb 2013 23:07:59 -0800 (PST)\r
+X-Spam-Scanned: at Caltech-IMSS on earth-doxen by amavisd-new\r
+Received: from finestructure.net (cpe-76-166-145-133.socal.res.rr.com\r
+       [76.166.145.133]) (Authenticated sender: jrollins)\r
+       by earth-doxen-submit (Postfix) with ESMTP id AD94666E00B8;\r
+       Mon, 11 Feb 2013 23:07:53 -0800 (PST)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+       id 1078D62219; Mon, 11 Feb 2013 23:07:53 -0800 (PST)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: David Bremner <david@tethera.net>,\r
+       Robert Mast <beheerder@tekenbeetziekten.nl>,\r
+       'Carl Worth' <cworth@cworth.org>,\r
+       'Jani Nikula' <jani@nikula.org>, notmuch@notmuchmail.org\r
+Subject: RE: Reply all - issue\r
+In-Reply-To: <87r4l2kvak.fsf@zancas.localnet>\r
+References: <000001cdfcd9$82500f00$86f02d00$@nl> <87wquxjq7k.fsf@nikula.org>\r
+       <002601cdfd83$83b283f0$8b178bd0$@nl>\r
+       <87boc8bt8a.fsf@yoom.home.cworth.org>\r
+       <000001cdff33$afe11070$0fa33150$@nl>\r
+       <87txpykve8.fsf@zancas.localnet> <87r4l2kvak.fsf@zancas.localnet>\r
+User-Agent: Notmuch/0.15+8~gd4a7374 (http://notmuchmail.org) Emacs/24.2.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Mon, 11 Feb 2013 23:07:50 -0800\r
+Message-ID: <87sj52nh6h.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha256; protocol="application/pgp-signature"\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\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: Tue, 12 Feb 2013 07:08:07 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+\r
+On Wed, Jan 30 2013, David Bremner <david@tethera.net> wrote:\r
+> Let me step back a level and say that special casing git patch series\r
+> strikes me as not yet seeing the problem in enough generality. Others\r
+> might disagree, of course.\r
+\r
+I agree with this statement.\r
+\r
+So I encounter the thread hijacking problem occasionally, but not\r
+frequently enough that I would trust a particular heuristic to cover it.\r
+I think I would prefer to just split hijacked threads manually as I\r
+encounter them.\r
+\r
+Just a thought: what if messages with a given tag (e.g. "new-thread")\r
+were always treated as the source of a new thread?  A message with the\r
+given tag could just be (re)indexed with any In-Reply-To/References\r
+headers stripped before indexing.  This would allow users to break\r
+threads manually, and it would mean dump && restore would always return\r
+the same state.\r
+\r
+The actual thread breaking, or specifically where it happens, would have\r
+to be thought through a bit.  Maybe this could be rolled into notmuch\r
+new somehow?  Or some other top-level function that applies operations\r
+to messages based on tags?\r
+\r
+jamie.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.12 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJRGepGAAoJEO00zqvie6q8ww0P+wfU3lZnpzMeX2xsygDyhrfv\r
+uxguQYOx744Nb3boVqkrKasRpJuuTXGkoyBvtnFHAD3EyExP1h/uE7YWBo8AULzd\r
+kxBgZdney4Z4UCxxPJpe4XJNjIEwTbuOR1691SU07GFshewI79/urC9jqiocUytO\r
+b6UhvwBXzK3qcqKgBgRmEYqO1V6Av7RdFjBSbL/ZiYn0nOc4y4oUi2dh2kB2gWeC\r
+n4YOsI1t2qV9b2Y+36SXBV7omX1a42CQJHLH/6mtGd2Oo3imIqdzsTW3kyZAhuJQ\r
+smBt4sxjYA79gvgUTlmw6tYIje2qhDbWbHFDUbb0kz0aZEqB4q+i04n5m4vdT4N3\r
+7lvoG/IHnQWI1LDX81n9DoaISbfJ36WyUU3151izHt/0l12cGpP/CAynG1jGziRx\r
+N2iq4DBWlqQBKno/qNnSMY9usvnoA9beX9q4hMVg7S/YnDQk1lK1ux95oPfYtLDd\r
+g/EUEDgMFwia4Dft6Q9yCG1v0IQP9Q3R2VDTshgXv0NutQg/Benj70EDZVaQZbbs\r
+kdCB8xo3RRTUWPkAVk8lUoe6zrLPlrkhQknFPkFHxgkvBVwALceNBSwvxL0IChch\r
+XaG9qukYgqrlh+Fly3dqXY97m6rhbT57EyALHJCYgSjPOCw9LXcxkRB8TvT6TLkS\r
+OXps5gD/O80wf9MV7hK7\r
+=7S0Z\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r