From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] sup crash when doing search
Date: Wed, 13 May 2009 09:50:24 +0100 [thread overview]
Message-ID: <1242204467-sup-6823@tomsk> (raw)
In-Reply-To: <1242198767-sup-3140@tomsk>
On 13.5.2009, I wrote:
> I can reproduce this, although this used to work. Not sure whats
> happening offhand but I'll poke around and see if I can fix it.
Ok, the crash doesnt happen in master only in next. The reason for the
crash is the new "limit" search option that doesnt check if chronic
has failed. Patch for that to follow (against next).
Theres also another bug in that Chronic should default to date
searches in the past as email is almost always dated earlier than your
current time (except spam). So theres a patch for that following as
well (against master)
Marcus
next prev parent reply other threads:[~2009-05-13 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 17:18 Damon Conway
2009-05-13 7:14 ` Marcus Williams
2009-05-13 8:50 ` Marcus Williams [this message]
2009-05-13 9:31 ` Marcus Williams
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=1242204467-sup-6823@tomsk \
--to=marcus-sup@bar-coded.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