1 Return-Path: <djcb@djcbsoftware.nl>
\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 033DA429E25
\r
6 for <notmuch@notmuchmail.org>; Fri, 4 Nov 2011 13:45:31 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.502 tagged_above=-999 required=5
\r
12 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,
\r
13 NML_ADSP_CUSTOM_MED=1.2, 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 CvucGfEcX+Zi for <notmuch@notmuchmail.org>;
\r
17 Fri, 4 Nov 2011 13:45:29 -0700 (PDT)
\r
18 X-Greylist: delayed 532 seconds by postgrey-1.32 at olra;
\r
19 Fri, 04 Nov 2011 13:45:29 PDT
\r
20 Received: from vs12.mail.saunalahti.fi (vs12.mail.saunalahti.fi
\r
22 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
23 (No client certificate requested)
\r
24 by olra.theworths.org (Postfix) with ESMTPS id 25393431FB6
\r
25 for <notmuch@notmuchmail.org>; Fri, 4 Nov 2011 13:45:29 -0700 (PDT)
\r
26 Received: from vams (localhost [127.0.0.1])
\r
27 by vs12.mail.saunalahti.fi (Postfix) with SMTP id 6F10324007D;
\r
28 Fri, 4 Nov 2011 22:36:32 +0200 (EET)
\r
29 Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi
\r
31 by vs12.mail.saunalahti.fi (Postfix) with ESMTP id 4A31E24007D;
\r
32 Fri, 4 Nov 2011 22:36:32 +0200 (EET)
\r
33 Received: from cthulhu.djcbsoftware.djcbsoftware.nl
\r
34 (a88-112-255-94.elisa-laajakaista.fi [88.112.255.94])
\r
35 (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
36 (No client certificate requested)
\r
37 by gw02.mail.saunalahti.fi (Postfix) with ESMTP id D93DE139C69;
\r
38 Fri, 4 Nov 2011 22:36:28 +0200 (EET)
\r
39 From: Dirk-Jan C. Binnema <djcb.bulk@gmail.com>
\r
40 To: Florian Friesdorf <flo@chaoflow.net>, Austin Clements <amdragon@mit.edu>
\r
41 Subject: Re: Re: thread ordering based on references and/or in-reply-to
\r
42 References: <87y5w0bvzn.fsf@eve.chaoflow.net>,
\r
43 <CAH-f9WuCVVtaA-TY9_Y5WXTYF56g_n19-T0Q6xJcCRU1E1COpw@mail.gmail.com>
\r
44 User-agent: mu 0.98pre; emacs 24.0.91.1
\r
46 <CAH-f9WuCVVtaA-TY9_Y5WXTYF56g_n19-T0Q6xJcCRU1E1COpw@mail.gmail.com>
\r
47 Date: Fri, 04 Nov 2011 22:36:15 +0200
\r
48 Message-ID: <8762izbp6o.fsf@cthulhu.djcbsoftware>
\r
50 Content-Type: text/plain
\r
51 Cc: notmuch@notmuchmail.org
\r
52 X-BeenThere: notmuch@notmuchmail.org
\r
53 X-Mailman-Version: 2.1.13
\r
55 Reply-To: djcb@djcbsoftware.nl
\r
56 List-Id: "Use and development of the notmuch mail system."
\r
57 <notmuch.notmuchmail.org>
\r
58 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
59 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
60 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
61 List-Post: <mailto:notmuch@notmuchmail.org>
\r
62 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
63 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
64 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
65 X-List-Received-Date: Fri, 04 Nov 2011 20:45:31 -0000
\r
69 On Wed 02 Nov 2011 04:37:05 PM EET, Austin Clements wrote:
\r
71 > On Mon, Oct 31, 2011 at 7:07 PM, Florian Friesdorf <flo@chaoflow.net> wrote:
\r
75 > > I'm looking into taking the References header into account for thread
\r
76 > > ordering. So far only In-Reply-To is used. My C/C++ is rusty at best, so
\r
77 > > I'd need some help to get this done.
\r
81 > I know this came up on IRC, but have you looked at jwz's threading
\r
82 > algorithm (http://www.jwz.org/doc/threading.html)? Carl mentioned
\r
83 > that notmuch already implements it (except for subject matching), but
\r
84 > notmuch only implements the subset of it necessary to group messages
\r
85 > into threads without structure. Much of the algorithm is devoted to
\r
86 > exactly this problem of piecing together the thread structure based on
\r
87 > all of the information in both In-Reply-To and References. The
\r
88 > algorithm as described combines the issues of grouping and structuring
\r
89 > since it's expecting a giant pile of mail as input, but there's no
\r
90 > reason these can't be teased apart.
\r
92 I've implemented it for mu[1], maybe some of it can be reusable for notmuch;
\r
93 see mu-threader.[ch] and mu-container.[ch] in
\r
95 http://gitorious.org/mu/mu/blobs/master/src/
\r
97 (starting point is mu_threader_calculate).
\r
99 I didn't implement subject matching yet, but it does build the hierarchy as
\r
100 per JWZ and "References:".
\r
106 Dirk-Jan C. Binnema Helsinki, Finland
\r
107 e:djcb@djcbsoftware.nl w:www.djcbsoftware.nl
\r
108 pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C
\r