1 Return-Path: <notmuch@kismala.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 52489431FB6
\r
6 for <notmuch@notmuchmail.org>; Wed, 6 Feb 2013 10:39:36 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id 7XDWHLgwVlkD for <notmuch@notmuchmail.org>;
\r
16 Wed, 6 Feb 2013 10:39:35 -0800 (PST)
\r
17 X-Greylist: delayed 1184 seconds by postgrey-1.32 at olra;
\r
18 Wed, 06 Feb 2013 10:39:35 PST
\r
19 Received: from imarko.xen.prgmr.com (imarko.xen.prgmr.com [72.13.95.244])
\r
20 by olra.theworths.org (Postfix) with ESMTP id 9F832431FAF
\r
21 for <notmuch@notmuchmail.org>; Wed, 6 Feb 2013 10:39:35 -0800 (PST)
\r
22 Received: from localhost ([127.0.0.1] helo=zsu.kismala.com)
\r
23 by imarko.xen.prgmr.com with esmtp (Exim 4.80.1)
\r
24 (envelope-from <notmuch@kismala.com>) id 1U39b4-0004Sa-G3
\r
25 for notmuch@notmuchmail.org; Wed, 06 Feb 2013 10:19:50 -0800
\r
26 From: Istvan Marko <notmuch@kismala.com>
\r
27 To: notmuch@notmuchmail.org
\r
28 Subject: Re: Reply all - issue
\r
29 References: <000001cdfcd9$82500f00$86f02d00$@nl>
\r
30 <CA+pa1O0mTxkj_FMQH_jXWajmUAKHWbMsB4Yhp_4UX7hnhwgBrg@mail.gmail.com>
\r
31 <000001ce0161$5da40990$18ec1cb0$@nl>
\r
32 <CA+pa1O3zdpz+43eJpsJwakV72_Fr5U4Dvk1ta1su7M701bx9mw@mail.gmail.com>
\r
33 Date: Wed, 06 Feb 2013 10:19:50 -0800
\r
35 <CA+pa1O3zdpz+43eJpsJwakV72_Fr5U4Dvk1ta1su7M701bx9mw@mail.gmail.com>
\r
36 (=?utf-8?Q?=22Micha=C5=82?= Nazarewicz"'s message of "Mon, 4 Feb 2013
\r
38 Message-ID: <m3d2wd2tkp.fsf@zsu.kismala.com>
\r
39 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.91 (gnu/linux)
\r
41 Content-Type: text/plain; charset=utf-8
\r
42 Content-Transfer-Encoding: quoted-printable
\r
43 X-BeenThere: notmuch@notmuchmail.org
\r
44 X-Mailman-Version: 2.1.13
\r
46 List-Id: "Use and development of the notmuch mail system."
\r
47 <notmuch.notmuchmail.org>
\r
48 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
49 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
50 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
51 List-Post: <mailto:notmuch@notmuchmail.org>
\r
52 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
53 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
54 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
55 X-List-Received-Date: Wed, 06 Feb 2013 18:39:36 -0000
\r
57 Micha=C5=82 Nazarewicz <mina86-deATy8a+UHjQT0dZR+AlfA@public.gmane.org>
\r
60 > I was actually wondering that instead of hard coding the logic into notmu=
\r
62 > itself, maybe it would be better to provide some sort of "split-thread" a=
\r
64 > "join-threads" which could than be used by separate tagging tool.
\r
66 Such a customized threading feature would be great, I would use it to
\r
67 tie together "loose threads" originating from crappy ticket tracking
\r
68 tools that don't insert any In-Reply-To or References headers. Currently
\r
69 I handle this by inserting fake In-Reply-To headers during delivery and
\r
70 I would love to have a cleaner way.
\r
72 To make this useful it would have to be persistent across dumps and
\r
75 If we only consider splitting then a relatively easy way might be to
\r
76 allow the user to configure some tags to mark a split. In
\r
77 .notmuch-config you'd have:
\r
81 And then you'd tag +split the message to mark the start of a new
\r
82 thread. The threading code would watch for such tags. Which might get
\r
83 hairy if the tag information is not already at hand during threading.
\r
85 I don't see how this would work for joins so it would not help me but it
\r
86 could address the original problem.
\r