From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup crash after a reply
Date: Sat, 19 Dec 2009 11:08:13 -0800 [thread overview]
Message-ID: <1261249617-sup-1685@masanjin.net> (raw)
In-Reply-To: <1260914644-sup-8154@bubs>
Reformatted excerpts from Vernon Mauery's message of 2009-12-15:
> I am running the latest git version of sup (as of yesterday) and I
> imported my 70000+ emails, archived most of them and have started to
> receive and send new mails.
I am going to throw this bug report in the big bucket of "weird Ferret
issues that will go away once we stop using Ferret."
In the mean time, you may want to switch to the Xapian backend.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-12-19 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 22:10 Vernon Mauery
2009-12-19 19:08 ` 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=1261249617-sup-1685@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@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