Re: Reply all - issue

diff --git a/c3/2e9ee85b8f3845a93fe92dbfc6754eecf88f10 b/c3/2e9ee85b8f3845a93fe92dbfc6754eecf88f10
new file mode 100644 (file)
index 0000000..1a8a9a9
--- /dev/null
+++ b/c3/2e9ee85b8f3845a93fe92dbfc6754eecf88f10
@@ -0,0 +1,89 @@
+Return-Path: <notmuch@kismala.com>\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 52489431FB6\r
+       for <notmuch@notmuchmail.org>; Wed,  6 Feb 2013 10:39:36 -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 7XDWHLgwVlkD for <notmuch@notmuchmail.org>;\r
+       Wed,  6 Feb 2013 10:39:35 -0800 (PST)\r
+X-Greylist: delayed 1184 seconds by postgrey-1.32 at olra;\r
+       Wed, 06 Feb 2013 10:39:35 PST\r
+Received: from imarko.xen.prgmr.com (imarko.xen.prgmr.com [72.13.95.244])\r
+       by olra.theworths.org (Postfix) with ESMTP id 9F832431FAF\r
+       for <notmuch@notmuchmail.org>; Wed,  6 Feb 2013 10:39:35 -0800 (PST)\r
+Received: from localhost ([127.0.0.1] helo=zsu.kismala.com)\r
+       by imarko.xen.prgmr.com with esmtp (Exim 4.80.1)\r
+       (envelope-from <notmuch@kismala.com>) id 1U39b4-0004Sa-G3\r
+       for notmuch@notmuchmail.org; Wed, 06 Feb 2013 10:19:50 -0800\r
+From: Istvan Marko <notmuch@kismala.com>\r
+To: notmuch@notmuchmail.org\r
+Subject: Re: Reply all - issue\r
+References: <000001cdfcd9$82500f00$86f02d00$@nl>\r
+       <CA+pa1O0mTxkj_FMQH_jXWajmUAKHWbMsB4Yhp_4UX7hnhwgBrg@mail.gmail.com>\r
+       <000001ce0161$5da40990$18ec1cb0$@nl>\r
+       <CA+pa1O3zdpz+43eJpsJwakV72_Fr5U4Dvk1ta1su7M701bx9mw@mail.gmail.com>\r
+Date: Wed, 06 Feb 2013 10:19:50 -0800\r
+In-Reply-To:\r
+ <CA+pa1O3zdpz+43eJpsJwakV72_Fr5U4Dvk1ta1su7M701bx9mw@mail.gmail.com>\r
+       (=?utf-8?Q?=22Micha=C5=82?= Nazarewicz"'s message of "Mon, 4 Feb 2013\r
+       11:39:44 +0100")\r
+Message-ID: <m3d2wd2tkp.fsf@zsu.kismala.com>\r
+User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.91 (gnu/linux)\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\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: Wed, 06 Feb 2013 18:39:36 -0000\r
+\r
+Micha=C5=82 Nazarewicz <mina86-deATy8a+UHjQT0dZR+AlfA@public.gmane.org>\r
+writes:\r
+\r
+> I was actually wondering that instead of hard coding the logic into notmu=\r
+ch\r
+> itself, maybe it would be better to provide some sort of "split-thread" a=\r
+nd\r
+> "join-threads" which could than be used by separate tagging tool.\r
+\r
+Such a customized threading feature would be great, I would use it to\r
+tie together "loose threads" originating from crappy ticket tracking\r
+tools that don't insert any In-Reply-To or References headers. Currently\r
+I handle this by inserting fake In-Reply-To headers during delivery and\r
+I would love to have a cleaner way.\r
+\r
+To make this useful it would have to be persistent across dumps and\r
+restores.=20\r
+\r
+If we only consider splitting then a relatively easy way might be to\r
+allow the user to configure some tags to mark a split. In\r
+.notmuch-config you'd have:\r
+\r
+split_tags: split\r
+\r
+And then you'd tag +split the message to mark the start of a new\r
+thread. The threading code would watch for such tags. Which might get\r
+hairy if the tag information is not already at hand during threading.\r
+\r
+I don't see how this would work for joins so it would not help me but it\r
+could address the original problem.\r
+\r
+--=20\r
+       Istvan\r