1 Return-Path: <mnazarewicz@gmail.com>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 3925D431FB6
\r
6 for <notmuch@notmuchmail.org>; Mon, 4 Feb 2013 02:39:49 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001,
\r
13 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id usJp0+xPCRjM for <notmuch@notmuchmail.org>;
\r
17 Mon, 4 Feb 2013 02:39:48 -0800 (PST)
\r
18 Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com
\r
19 [209.85.217.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id F1B2E431FAE
\r
22 for <notmuch@notmuchmail.org>; Mon, 4 Feb 2013 02:39:47 -0800 (PST)
\r
23 Received: by mail-lb0-f169.google.com with SMTP id m4so6569592lbo.0
\r
24 for <notmuch@notmuchmail.org>; Mon, 04 Feb 2013 02:39:45 -0800 (PST)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
\r
26 h=mime-version:x-received:sender:in-reply-to:references:date
\r
27 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
\r
28 bh=LZQRR7999u2s2zLHdrWW6OBVBck+rBTTDEUvUSmA7/c=;
\r
29 b=d/n5oU1+WQF1pgA+FZH/TvJqn9sVn9x+jGKqYYvlbL7ZGojqFn5oeUp3GGmAzkmZ6N
\r
30 Va99uCorti4KiAs6BAfHCbTVmZ4GV03MNP2XydnJQGFaqKy8afxWgK1vhWqQ6QQuN90r
\r
31 FS/SDSZq0mpboZgohQSRx5KKkoUds15lCMkvThqc6Na44Pa1RQfS17dNMjs6wBoZwYaY
\r
32 VAhJoWoGFvWz0OQ2FMVR9eK6l/KdrJRpLjYPo+ksOKd1QJ85JqW/yL3T1ytR9OasTLje
\r
33 Oo4Eh/TGQ0q9eretETiDVw8iyThYz7AfEVwBjKct5lmvbrG36ICqkv4LOp7mOD462bmW
\r
36 X-Received: by 10.112.23.136 with SMTP id m8mr8082038lbf.53.1359974384828;
\r
37 Mon, 04 Feb 2013 02:39:44 -0800 (PST)
\r
38 Sender: mnazarewicz@gmail.com
\r
39 Received: by 10.114.99.65 with HTTP; Mon, 4 Feb 2013 02:39:44 -0800 (PST)
\r
40 Received: by 10.114.99.65 with HTTP; Mon, 4 Feb 2013 02:39:44 -0800 (PST)
\r
41 In-Reply-To: <000001ce0161$5da40990$18ec1cb0$@nl>
\r
42 References: <000001cdfcd9$82500f00$86f02d00$@nl>
\r
43 <CA+pa1O0mTxkj_FMQH_jXWajmUAKHWbMsB4Yhp_4UX7hnhwgBrg@mail.gmail.com>
\r
44 <000001ce0161$5da40990$18ec1cb0$@nl>
\r
45 Date: Mon, 4 Feb 2013 11:39:44 +0100
\r
46 X-Google-Sender-Auth: 57rVVK4hNkAOjgCZ9gT3QZCOvtA
\r
48 <CA+pa1O3zdpz+43eJpsJwakV72_Fr5U4Dvk1ta1su7M701bx9mw@mail.gmail.com>
\r
49 Subject: RE: Reply all - issue
\r
50 From: =?UTF-8?Q?Micha=C5=82_Nazarewicz?= <mina86@mina86.com>
\r
51 To: Robert Mast <beheerder@tekenbeetziekten.nl>
\r
52 Content-Type: multipart/alternative; boundary=e0cb4efe304a1c828704d4e3b659
\r
53 Cc: notmuch@notmuchmail.org
\r
54 X-BeenThere: notmuch@notmuchmail.org
\r
55 X-Mailman-Version: 2.1.13
\r
57 List-Id: "Use and development of the notmuch mail system."
\r
58 <notmuch.notmuchmail.org>
\r
59 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
60 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
61 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
62 List-Post: <mailto:notmuch@notmuchmail.org>
\r
63 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
64 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
65 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
66 X-List-Received-Date: Mon, 04 Feb 2013 10:39:49 -0000
\r
68 --e0cb4efe304a1c828704d4e3b659
\r
69 Content-Type: text/plain; charset=UTF-8
\r
70 Content-Transfer-Encoding: quoted-printable
\r
72 2 lut 2013 17:21, "Robert Mast" <beheerder@tekenbeetziekten.nl> napisa=C5=
\r
74 > So Gmail-threading is still the best I suppose,
\r
76 I strongly disagree. Having said that, as long as it's configurable I
\r
77 obviously won't be blocking your efforts.
\r
79 > Anyone interested in me patching Notmuch, or shall I keep the changes to
\r
82 I was actually wondering that instead of hard coding the logic into notmuch
\r
83 itself, maybe it would be better to provide some sort of "split-thread" and
\r
84 "join-threads" which could than be used by separate tagging tool.
\r
86 To be user-friendly this may require a possibly to search for all ancestors
\r
87 of a given message and possibly an option to sort results topologically
\r
88 which I dunno if notmuch has.
\r
90 --e0cb4efe304a1c828704d4e3b659
\r
91 Content-Type: text/html; charset=UTF-8
\r
92 Content-Transfer-Encoding: quoted-printable
\r
94 <p dir=3D"ltr">2 lut 2013 17:21, "Robert Mast" <<a href=3D"mai=
\r
95 lto:beheerder@tekenbeetziekten.nl">beheerder@tekenbeetziekten.nl</a>> na=
\r
97 > So Gmail-threading is still the best I suppose, </p>
\r
98 <p dir=3D"ltr">I strongly disagree. Having said that, as long as it's c=
\r
99 onfigurable I obviously won't be blocking your efforts. </p>
\r
100 <p dir=3D"ltr">> Anyone interested in me patching Notmuch, or shall I ke=
\r
101 ep the changes to myself?</p>
\r
102 <p dir=3D"ltr">I was actually wondering that instead of hard coding the log=
\r
103 ic into notmuch itself, maybe it would be better to provide some sort of &q=
\r
104 uot;split-thread" and "join-threads" which could than be use=
\r
105 d by separate tagging tool.</p>
\r
107 <p dir=3D"ltr">To be user-friendly this may require a possibly to search fo=
\r
108 r all ancestors of a given message and possibly an option to sort results t=
\r
109 opologically which I dunno if notmuch has. </p>
\r
111 --e0cb4efe304a1c828704d4e3b659--
\r