RE: Reply all - issue

diff --git a/e4/3a51fcea9cd7760f804b12f96603471d049360 b/e4/3a51fcea9cd7760f804b12f96603471d049360
new file mode 100644 (file)
index 0000000..b3e898e
--- /dev/null
+++ b/e4/3a51fcea9cd7760f804b12f96603471d049360
@@ -0,0 +1,111 @@
+Return-Path: <bremner@unb.ca>\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 95561431FB6\r
+       for <notmuch@notmuchmail.org>; Sat,  2 Feb 2013 12:52:51 -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 6lADadiOXmDE for <notmuch@notmuchmail.org>;\r
+       Sat,  2 Feb 2013 12:52:49 -0800 (PST)\r
+Received: from tesseract.cs.unb.ca (tesseract.cs.unb.ca [131.202.240.238])\r
+       (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id B773D431FAE\r
+       for <notmuch@notmuchmail.org>; Sat,  2 Feb 2013 12:52:49 -0800 (PST)\r
+Received: from fctnnbsc30w-156034082078.dhcp-dynamic.fibreop.nb.bellaliant.net\r
+       ([156.34.82.78] helo=zancas.localnet)\r
+       by tesseract.cs.unb.ca with esmtpsa\r
+       (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80)\r
+       (envelope-from <bremner@unb.ca>)\r
+       id 1U1k4p-0006yI-B7; Sat, 02 Feb 2013 16:52:46 -0400\r
+Received: from bremner by zancas.localnet with local (Exim 4.80)\r
+       (envelope-from <bremner@unb.ca>)\r
+       id 1U1k4j-00029G-Js; Sat, 02 Feb 2013 16:52:37 -0400\r
+From: David Bremner <david@tethera.net>\r
+To: Robert Mast <beheerder@tekenbeetziekten.nl>\r
+Subject: RE: Reply all - issue\r
+In-Reply-To: <000001ce0161$5da40990$18ec1cb0$@nl>\r
+References: <000001cdfcd9$82500f00$86f02d00$@nl>\r
+       <CA+pa1O0mTxkj_FMQH_jXWajmUAKHWbMsB4Yhp_4UX7hnhwgBrg@mail.gmail.com>\r
+       <000001ce0161$5da40990$18ec1cb0$@nl>\r
+User-Agent: Notmuch/0.15.1 (http://notmuchmail.org) Emacs/24.2.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sat, 02 Feb 2013 16:52:37 -0400\r
+Message-ID: <87a9rml9pm.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-Spam_bar: -\r
+Cc: notmuch@notmuchmail.org\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: Sat, 02 Feb 2013 20:52:51 -0000\r
+\r
+Robert Mast <beheerder@tekenbeetziekten.nl> writes:\r
+\r
+>\r
+> Anyone interested in me patching Notmuch, or shall I keep the changes\r
+> to myself?\r
+>\r
+\r
+Hi Robert;\r
+\r
+If you have patches, and you want feedback on them, then you are of\r
+course welcome to send them to the list.  Previous experience suggests\r
+us that it is often faster in the long run (in terms of actually getting\r
+code into notmuch) to take time to work out the design issues before\r
+starting coding. Some suggestions/comments:\r
+\r
+1) See http://notmuchmail.org/contributing/ for some general hints on\r
+   contributing code to notmuch.\r
+             \r
+2) Make sure whatever threading heuristic you use is deterministic, and\r
+   robust in the face of messages arriving in different orders, and\r
+   munging of headers by mailing lists (subjects in particular get\r
+   munged fairly often).  \r
+\r
+3) In particular, it seems important that "notmuch dump" followed by\r
+   "notmuch restore" (possibly followed by notmuch new?) yields unchanged\r
+   or equivalent thread structure\r
+\r
+4) Since threading heuristics are a matter of taste (i.e. not everyone\r
+   is convinced that the way Gmail does it is the way notmuch should),\r
+   you'll need to make this configurable. One constraint is that the\r
+   library itself (under ./lib) is should not read configuration files\r
+   (or environment variables, although it violates this for debugging).\r
+   This just means you will have to change the API to pass configuration\r
+   information in to certain routines.\r
+\r
+5) I'd say it's more important that you can shut off the heuristic\r
+   completely than have special handling for git (or other version\r
+   control system) patch series.  If you do decide to add some special\r
+   handling for patch series, I'd suggest making it as generic as\r
+   possible, perhaps a configurable list of (header, regex) values that\r
+   disable the thread splitting heuristics.\r
+\r
+6) Decide how, if at all your design will support manually joining\r
+   threads together.  I think an acceptable answer would probably be\r
+   "disable all thread splitting heuristics and rebuild the\r
+   database". I'm not sure if it's feasible to do anything nicer than\r
+   that.\r
+\r
+d\r
+\r
+\r
+\r