From: Anthony Martinez <pi+sup@pihost.us>
To: sup-devel <sup-talk@rubyforge.org>
Subject: [sup-talk] Ferret to Xapian conversion
Date: Sat, 02 Jan 2010 13:06:16 -0700 [thread overview]
Message-ID: <1262460996-sup-1383@home.mrtheplague.net> (raw)
Ferret is starting to give me trouble (StateErrors when I'm marking messages in
the Unread mode as read), so I figure that there is no better time to convert to
Xapian. However, the documentation on the Wiki hasn't been updated since
(September of) last year.
A quick glance over the recent patches doesn't suggest anything that would break
the procedure on the Wiki, and I assume that Rich Lane and others are running on
Xapian without excessive trouble, so the only difference from the Wiki is that
we can run sup without -o and rm -rf ~/.sup/ferret nowadays.
Is that an accurate assessment?
-- Anthony
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-01-02 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 20:06 Anthony Martinez [this message]
2010-01-02 21:24 ` William Morgan
2010-01-02 22:34 ` William Morgan
2010-01-03 15:18 ` William Morgan
2010-01-03 19:38 ` [sup-devel] " Anthony Martinez
2010-01-03 20:18 ` Rich Lane
2010-01-03 22:47 ` Anthony Martinez
2010-01-03 23:52 ` Kevin Riggle
2010-01-05 21:15 ` William Morgan
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=1262460996-sup-1383@home.mrtheplague.net \
--to=pi+sup@pihost.us \
--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