From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] XapianIndex.each_message_in_thread_for yields messages in cronological order
Date: Wed, 30 Dec 2009 06:10:54 -0800 [thread overview]
Message-ID: <1262182085-sup-1405@masanjin.net> (raw)
In-Reply-To: <1262136474-sup-312@tilus.net>
Reformatted excerpts from Tero Tilus's message of 2009-12-29:
> For what I know you might trigger this by replying to many messages at
> once and thus having a list of ids in-reply-to header (in whatever
> order of course, rfc doesn't require any particular order) instead of
> one. Then when you reply to this message using MUA that is bold
> enough to try to form References: with the standard in-reply-to +
> my-id method even if RFC 2822 says "trying to form a References: field
> for a reply that has multiple parents is discouraged and how to do so
> is not defined in this document". You end up having References: which
> has bunch of (thread-wise) random ids in random order instead of the
> rfc-specified original, reply, replytoreply, etc. chain of ids.
It's worth reading the top bit of http://www.jwz.org/doc/threading.html
for what In-reply-to: and References: look like in practice. (Basically:
a mess, and the references: header in particular can be truncated in any
way that any MUA feels is reasonable.)
The threading used by the Ferret indexer is a pretty faithful
reproduction of the algorithm described on that page. I'm not that
familiar with the one used by the Xapian index, but a cursory
examination suggests it's a little more fragile.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2009-12-30 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1261485246-sup-4236@tilus.net>
2009-12-27 21:37 ` Rich Lane
2009-12-30 2:41 ` Tero Tilus
2009-12-30 14:10 ` William Morgan [this message]
2009-12-30 17:01 ` Rich Lane
2009-12-31 19:41 ` William Morgan
2010-01-01 13:19 ` Tero Tilus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1262182085-sup-1405@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox