Re: Fix missing References from broken muas.

diff --git a/86/20e6b89c9fdd5918982eb6bb7676025174bd0a b/86/20e6b89c9fdd5918982eb6bb7676025174bd0a
new file mode 100644 (file)
index 0000000..7b09843
--- /dev/null
+++ b/86/20e6b89c9fdd5918982eb6bb7676025174bd0a
@@ -0,0 +1,93 @@
+Return-Path: <cworth@cworth.org>\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 BEF1440D166\r
+       for <notmuch@notmuchmail.org>; Fri, 29 Oct 2010 13:23:28 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.89\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5\r
+       tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01]\r
+       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 ULfSpr5utNqb; Fri, 29 Oct 2010 13:23:18 -0700 (PDT)\r
+Received: from yoom.home.cworth.org (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 800D840D164;\r
+       Fri, 29 Oct 2010 13:23:18 -0700 (PDT)\r
+Received: by yoom.home.cworth.org (Postfix, from userid 1000)\r
+       id 278F92540F4; Fri, 29 Oct 2010 13:23:18 -0700 (PDT)\r
+From: Carl Worth <cworth@cworth.org>\r
+To: Arvid Picciani <aep@exys.org>, notmuch@notmuchmail.org\r
+Subject: Re: Fix missing References from broken muas.\r
+In-Reply-To: <87pr16efjp.fsf@exys.org>\r
+References: <87pr16efjp.fsf@exys.org>\r
+User-Agent: Notmuch/0.3.1-137-gce6390c (http://notmuchmail.org) Emacs/23.2.1\r
+       (i486-pc-linux-gnu)\r
+Date: Fri, 29 Oct 2010 13:23:17 -0700\r
+Message-ID: <87vd4k6956.fsf@yoom.home.cworth.org>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha1; 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: Fri, 29 Oct 2010 20:23:28 -0000\r
+\r
+--=-=-=\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Sat, 08 May 2010 14:36:26 +0200, Arvid Picciani <aep@exys.org> wrote:\r
+> Most of my mail comes from the 50MLs i'm subscribed to. Unfortunately\r
+> some MUAs suck that much, they don't even respond in threads.\r
+> My idea how to fix them would be:\r
+\r
+People have previously asked for a feature to combine messages into the\r
+same thread.\r
+\r
+And it would actually be a fairly simple operation. Perhaps it could be\r
+something like:\r
+\r
+notmuch set-thread $(notmuch search --threads <parent>) <children>\r
+\r
+The bigger problem is that as soon as we have an operation to join\r
+threads, people are going to need an operation to split threads. (And\r
+some people want this already for cases where people reply when they\r
+should have composed a new message.)\r
+\r
+The split case is harder in that it will require some extra stashing of\r
+information about the intent of the split, (otherwise, the current logic\r
+will recombine things when a future message arrives that References:\r
+messages from two split threads).\r
+\r
+So I think we'd need a proposal to handle that before we could do\r
+splitting. The proposal I'm looking for here would be at the database\r
+level, not the command-line level.\r
+\r
+=2DCarl\r
+\r
+=2D-=20\r
+carl.d.worth@intel.com\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.10 (GNU/Linux)\r
+\r
+iD8DBQFMyy016JDdNq8qSWgRAgGjAJ9gADD5o07r+GNAitv11mUaMXR7VQCdEMXS\r
+HEAnRYpmN+OQG2awj9w/rGY=\r
+=yi8F\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r