From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Too many clauses
Date: Sun, 09 Dec 2007 18:54:43 -0800 [thread overview]
Message-ID: <1197255121-sup-2562@south> (raw)
In-Reply-To: <1197249489-sup-4661@Nyx>
Excerpts from Dennis Griffith's message of Sun Dec 09 17:31:23 -0800 2007:
> I could, although I wouldn't be able to tell you if it works anymore.
> After installing 0.3 again, in preparation for trying the patch, I
> found I no longer hit the problem. I haven't updated ferret during
> this time, so perhaps my message count has fallen low enough not to
> trigger the problem, if I hit this again I will try the patch and let
> you know.
Weird. I think this problem surfaces with very large threads, so it
shouldn't have anything to do with raw message count.
But all's well that ends well. I've committed the patch to SVN anyways
because it's probably the right thing to do. (And is a better solution
than just increasing the Ferret thingy.)
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-12-10 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 19:52 Dennis Griffith
2007-12-09 19:44 ` William Morgan
2007-12-10 1:31 ` Dennis Griffith
2007-12-10 2:54 ` William Morgan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1197255121-sup-2562@south \
--to=wmorgan-sup@masanjin.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