From: Rich Lane <rlane@club.cc.cmu.edu>
To: Tero Tilus <tero@tilus.net>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] XapianIndex.each_message_in_thread_for yields messages in cronological order
Date: Sun, 27 Dec 2009 16:37:37 -0500 [thread overview]
Message-ID: <1261938751-sup-9421@zyrg.net> (raw)
In-Reply-To: <1261485246-sup-4236@tilus.net>
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
next parent reply other threads:[~2009-12-27 21:37 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 [this message]
2009-12-30 2:41 ` Tero Tilus
2009-12-30 14:10 ` William Morgan
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=1261938751-sup-9421@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=sup-devel@rubyforge.org \
--cc=tero@tilus.net \
/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