Re: [sup-devel] [PATCH] XapianIndex.each_message_in_thread_for yields messages in cronological order

[Rich Lane <rlane@club.cc.cmu.edu>]

Excerpts from Tero Tilus's message of Tue Dec 22 07:42:52 -0500 2009:
> This way I got rid of a couple of counterintuitive threading results.
> Namely real root of a thread would occasionally not be displayed as a
> root if a message containing the real root in the middle of its
> refs-list (dunno why) would get yielded (to threading algorithm)
> before the real root.  Threading algorithm looks like it silently
> expects threaded messages to appear in cronological order.

Hmm. Threading should only depend on refs and reply-tos, not the date.
Could you give a short example (just the relevant headers) of a
situation where this patch helps?

What you describe sounds like a malformed message. What client is
generating them / how common are they?
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel