RE: Reply all - issue

diff --git a/2c/eb566b3ee1b377742b5bfed58078f555ab78dd b/2c/eb566b3ee1b377742b5bfed58078f555ab78dd
new file mode 100644 (file)
index 0000000..a2fe34e
--- /dev/null
+++ b/2c/eb566b3ee1b377742b5bfed58078f555ab78dd
@@ -0,0 +1,77 @@
+Return-Path: <beheerder@tekenbeetziekten.nl>\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 D44BB431FB6\r
+       for <notmuch@notmuchmail.org>; Mon, 28 Jan 2013 10:16:03 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\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 3ONViV9yISjS for <notmuch@notmuchmail.org>;\r
+       Mon, 28 Jan 2013 10:15:59 -0800 (PST)\r
+Received: from srv047132.webreus.nl (srv047132.webreus.nl [46.235.47.132])\r
+       (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id F2033431FAE\r
+       for <notmuch@notmuchmail.org>; Mon, 28 Jan 2013 10:15:58 -0800 (PST)\r
+Received: (qmail 21730 invoked from network); 28 Jan 2013 19:15:57 +0100\r
+Received: from 87-251-48-4.lombox.customer.bit.nl (HELO WBNL79005)\r
+       (87.251.48.4)\r
+       by srv047132.webreus.nl with SMTP; 28 Jan 2013 19:15:57 +0100\r
+From: "Robert Mast" <beheerder@tekenbeetziekten.nl>\r
+To: "'Jani Nikula'" <jani@nikula.org>,\r
+       <notmuch@notmuchmail.org>\r
+References: <000001cdfcd9$82500f00$86f02d00$@nl> <87wquxjq7k.fsf@nikula.org>\r
+In-Reply-To: <87wquxjq7k.fsf@nikula.org>\r
+Subject: RE: Reply all - issue\r
+Date: Mon, 28 Jan 2013 19:15:55 +0100\r
+Message-ID: <002601cdfd83$83b283f0$8b178bd0$@nl>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain;\r
+       charset="US-ASCII"\r
+Content-Transfer-Encoding: 7bit\r
+X-Mailer: Microsoft Office Outlook 12.0\r
+Thread-Index: Ac39agg6riWfWJCKSlivo9D6sTE32AAFOTnA\r
+Content-Language: nl\r
+X-Mailman-Approved-At: Mon, 28 Jan 2013 18:19:02 -0800\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: Mon, 28 Jan 2013 18:16:04 -0000\r
+\r
+Thanks for your reply.\r
+\r
+I never tried gmail-conversation threading, but from your first reference I\r
+understand it breaks threads on subject unconditionally.\r
+\r
+Breaking on subject unconditionally would be even easier to implement, as\r
+comparing the contents of previous messages takes performance and as long as\r
+the crucial linking messages aren't read the outcome is ambiguous and would\r
+lead to the annoying jumping of results.\r
+\r
+I'll watch for 'client-end' solutions, but the mail that broke all those\r
+mailers originated from my own mailprogram, I think Outlook 2010, so\r
+automatic clearing references and in-reply-to when the user clears the\r
+subject and body isn't common practice for MUA's.\r
+\r
+Your point on patch-breaking related to gmail and my proposal isn't\r
+completely clear to me, but I've probably addressed it well with my new\r
+approach.\r
+\r
+I'll study the code for adding the option of unconditional (stripped)\r
+subject breaking on top of the existing thread-breaking.\r
+\r