From: Dirk-Jan C. Binnema <djcb.bulk@gmail.com>
To: Florian Friesdorf <flo@chaoflow.net>, Austin Clements <amdragon@mit.edu>
Cc: notmuch@notmuchmail.org
Subject: Re: Re: thread ordering based on references and/or in-reply-to
Date: Fri, 04 Nov 2011 22:36:15 +0200 [thread overview]
Message-ID: <8762izbp6o.fsf@cthulhu.djcbsoftware> (raw)
In-Reply-To: <CAH-f9WuCVVtaA-TY9_Y5WXTYF56g_n19-T0Q6xJcCRU1E1COpw@mail.gmail.com>
On Wed 02 Nov 2011 04:37:05 PM EET, Austin Clements wrote:
> On Mon, Oct 31, 2011 at 7:07 PM, Florian Friesdorf <flo@chaoflow.net> wrote:
> >
> > Hi,
> >
> > I'm looking into taking the References header into account for thread
> > ordering. So far only In-Reply-To is used. My C/C++ is rusty at best, so
> > I'd need some help to get this done.
<snip>
> I know this came up on IRC, but have you looked at jwz's threading
> algorithm (http://www.jwz.org/doc/threading.html)? Carl mentioned
> that notmuch already implements it (except for subject matching), but
> notmuch only implements the subset of it necessary to group messages
> into threads without structure. Much of the algorithm is devoted to
> exactly this problem of piecing together the thread structure based on
> all of the information in both In-Reply-To and References. The
> algorithm as described combines the issues of grouping and structuring
> since it's expecting a giant pile of mail as input, but there's no
> reason these can't be teased apart.
I've implemented it for mu[1], maybe some of it can be reusable for notmuch;
see mu-threader.[ch] and mu-container.[ch] in
http://gitorious.org/mu/mu/blobs/master/src/
(starting point is mu_threader_calculate).
I didn't implement subject matching yet, but it does build the hierarchy as
per JWZ and "References:".
Best wishes,
Dirk.
--
Dirk-Jan C. Binnema Helsinki, Finland
e:djcb@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C
prev parent reply other threads:[~2011-11-04 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 23:07 thread ordering based on references and/or in-reply-to Florian Friesdorf
2011-11-02 14:37 ` Austin Clements
2011-11-04 20:36 ` Dirk-Jan C. Binnema [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8762izbp6o.fsf@cthulhu.djcbsoftware \
--to=djcb.bulk@gmail.com \
--cc=amdragon@mit.edu \
--cc=djcb@djcbsoftware.nl \
--cc=flo@chaoflow.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).