--- /dev/null
+Return-Path: <mnazarewicz@gmail.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 3925D431FB6\r
+ for <notmuch@notmuchmail.org>; Mon, 4 Feb 2013 02:39:49 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.698\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5\r
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001,\r
+ HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 usJp0+xPCRjM for <notmuch@notmuchmail.org>;\r
+ Mon, 4 Feb 2013 02:39:48 -0800 (PST)\r
+Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com\r
+ [209.85.217.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id F1B2E431FAE\r
+ for <notmuch@notmuchmail.org>; Mon, 4 Feb 2013 02:39:47 -0800 (PST)\r
+Received: by mail-lb0-f169.google.com with SMTP id m4so6569592lbo.0\r
+ for <notmuch@notmuchmail.org>; Mon, 04 Feb 2013 02:39:45 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=mime-version:x-received:sender:in-reply-to:references:date\r
+ :x-google-sender-auth:message-id:subject:from:to:cc:content-type;\r
+ bh=LZQRR7999u2s2zLHdrWW6OBVBck+rBTTDEUvUSmA7/c=;\r
+ b=d/n5oU1+WQF1pgA+FZH/TvJqn9sVn9x+jGKqYYvlbL7ZGojqFn5oeUp3GGmAzkmZ6N\r
+ Va99uCorti4KiAs6BAfHCbTVmZ4GV03MNP2XydnJQGFaqKy8afxWgK1vhWqQ6QQuN90r\r
+ FS/SDSZq0mpboZgohQSRx5KKkoUds15lCMkvThqc6Na44Pa1RQfS17dNMjs6wBoZwYaY\r
+ VAhJoWoGFvWz0OQ2FMVR9eK6l/KdrJRpLjYPo+ksOKd1QJ85JqW/yL3T1ytR9OasTLje\r
+ Oo4Eh/TGQ0q9eretETiDVw8iyThYz7AfEVwBjKct5lmvbrG36ICqkv4LOp7mOD462bmW\r
+ z4lg==\r
+MIME-Version: 1.0\r
+X-Received: by 10.112.23.136 with SMTP id m8mr8082038lbf.53.1359974384828;\r
+ Mon, 04 Feb 2013 02:39:44 -0800 (PST)\r
+Sender: mnazarewicz@gmail.com\r
+Received: by 10.114.99.65 with HTTP; Mon, 4 Feb 2013 02:39:44 -0800 (PST)\r
+Received: by 10.114.99.65 with HTTP; Mon, 4 Feb 2013 02:39:44 -0800 (PST)\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
+Date: Mon, 4 Feb 2013 11:39:44 +0100\r
+X-Google-Sender-Auth: 57rVVK4hNkAOjgCZ9gT3QZCOvtA\r
+Message-ID:\r
+ <CA+pa1O3zdpz+43eJpsJwakV72_Fr5U4Dvk1ta1su7M701bx9mw@mail.gmail.com>\r
+Subject: RE: Reply all - issue\r
+From: =?UTF-8?Q?Micha=C5=82_Nazarewicz?= <mina86@mina86.com>\r
+To: Robert Mast <beheerder@tekenbeetziekten.nl>\r
+Content-Type: multipart/alternative; boundary=e0cb4efe304a1c828704d4e3b659\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: Mon, 04 Feb 2013 10:39:49 -0000\r
+\r
+--e0cb4efe304a1c828704d4e3b659\r
+Content-Type: text/plain; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+2 lut 2013 17:21, "Robert Mast" <beheerder@tekenbeetziekten.nl> napisa=C5=\r
+=82(a):\r
+> So Gmail-threading is still the best I suppose,\r
+\r
+I strongly disagree. Having said that, as long as it's configurable I\r
+obviously won't be blocking your efforts.\r
+\r
+> Anyone interested in me patching Notmuch, or shall I keep the changes to\r
+myself?\r
+\r
+I was actually wondering that instead of hard coding the logic into notmuch\r
+itself, maybe it would be better to provide some sort of "split-thread" and\r
+"join-threads" which could than be used by separate tagging tool.\r
+\r
+To be user-friendly this may require a possibly to search for all ancestors\r
+of a given message and possibly an option to sort results topologically\r
+which I dunno if notmuch has.\r
+\r
+--e0cb4efe304a1c828704d4e3b659\r
+Content-Type: text/html; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+<p dir=3D"ltr">2 lut 2013 17:21, "Robert Mast" <<a href=3D"mai=\r
+lto:beheerder@tekenbeetziekten.nl">beheerder@tekenbeetziekten.nl</a>> na=\r
+pisa=C5=82(a):<br>\r
+> So Gmail-threading is still the best I suppose, </p>\r
+<p dir=3D"ltr">I strongly disagree. Having said that, as long as it's c=\r
+onfigurable I obviously won't be blocking your efforts. </p>\r
+<p dir=3D"ltr">> Anyone interested in me patching Notmuch, or shall I ke=\r
+ep the changes to myself?</p>\r
+<p dir=3D"ltr">I was actually wondering that instead of hard coding the log=\r
+ic into notmuch itself, maybe it would be better to provide some sort of &q=\r
+uot;split-thread" and "join-threads" which could than be use=\r
+d by separate tagging tool.</p>\r
+\r
+<p dir=3D"ltr">To be user-friendly this may require a possibly to search fo=\r
+r all ancestors of a given message and possibly an option to sort results t=\r
+opologically which I dunno if notmuch has. </p>\r
+\r
+--e0cb4efe304a1c828704d4e3b659--\r