1 Return-Path: <cworth@cworth.org>
\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 63F83431FBC;
\r
6 Thu, 10 Dec 2009 10:16:36 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id 18abKxjFBGc1; Thu, 10 Dec 2009 10:16:35 -0800 (PST)
\r
11 Received: from yoom.home.cworth.org (localhost [127.0.0.1])
\r
12 by olra.theworths.org (Postfix) with ESMTP id BDB4A431FAE;
\r
13 Thu, 10 Dec 2009 10:16:35 -0800 (PST)
\r
14 Received: by yoom.home.cworth.org (Postfix, from userid 1000)
\r
15 id 0141F2542FF; Thu, 10 Dec 2009 09:39:54 -0800 (PST)
\r
16 From: Carl Worth <cworth@cworth.org>
\r
17 To: Mark Anderson <markr.anderson@amd.com>, notmuch <notmuch@notmuchmail.org>
\r
18 In-Reply-To: <1260400470-sup-5775@testarossa>
\r
19 References: <1260400470-sup-5775@testarossa>
\r
20 Date: Thu, 10 Dec 2009 09:39:48 -0800
\r
21 Message-ID: <87ws0ug23f.fsf@yoom.home.cworth.org>
\r
23 Content-Type: multipart/signed; boundary="=-=-=";
\r
24 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
25 Subject: Re: [notmuch] Threading
\r
26 X-BeenThere: notmuch@notmuchmail.org
\r
27 X-Mailman-Version: 2.1.12
\r
29 List-Id: "Use and development of the notmuch mail system."
\r
30 <notmuch.notmuchmail.org>
\r
31 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
32 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
33 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
34 List-Post: <mailto:notmuch@notmuchmail.org>
\r
35 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
36 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
37 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
38 X-List-Received-Date: Thu, 10 Dec 2009 18:16:36 -0000
\r
42 On Wed, 9 Dec 2009 16:21:34 -0700, Mark Anderson <markr.anderson@amd.com> wrote:
\r
43 > I was wondering if there's a way in notmuch to group un-associated
\r
44 > threads into a single thread.
\r
46 There's certainly nothing like that in notmuch currently.
\r
48 Sup had user-level functionality in the interface for stitching messages
\r
49 into a single thread, and I definitely think that that doesn't make any
\r
52 > I have a bug tracking system that doesn't give me emails that thread naturally in notmuch.
\r
54 I've seen similar things. Bugzilla emails at least all group into a
\r
55 single thread in notmuch, but don't get nested correctly at all, and
\r
56 that's really annoying.
\r
58 > I wouldn't mind writing a filter that could help identify a thread id
\r
59 > which should apply to a message, and suggest that to notmuch.
\r
61 I think the right answer here is to fix the input that notmuch is
\r
62 getting. Just ensure that each message has a proper In-Reply-To header
\r
63 and all should be fine. If you can't fix the bug-tracking system to emit
\r
64 proper email, can you apply your filter and rewrite the message as part
\r
65 of delivery (before notmuch sees it)?
\r
70 Content-Type: application/pgp-signature
\r
72 -----BEGIN PGP SIGNATURE-----
\r
73 Version: GnuPG v1.4.10 (GNU/Linux)
\r
75 iD8DBQFLITJl6JDdNq8qSWgRAqjzAKCnCZsa7lTzORmfKbBrQmppkwXnDgCdHdtL
\r
76 52r8Bi4++WdJfuG7UiP1NjQ=
\r
78 -----END PGP SIGNATURE-----
\r