From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Ferret to Xapian conversion
Date: Sun, 03 Jan 2010 07:18:53 -0800 [thread overview]
Message-ID: <1262531773-sup-5192@masanjin.net> (raw)
In-Reply-To: <1262471675-sup-1708@masanjin.net>
If you pull the latest git next, there should be a
sup-convert-ferret-index script which should automate this process. (You
will also start getting yelled at for using Ferret.)
If you run this script, please report your experience, since I'd like to
include it in the 0.10 release coming soon.
It doesn't remove your old .ferret directory, so if anything goes wrong
(unlikely, but hey), you should be able to recover.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-01-03 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 20:06 Anthony Martinez
2010-01-02 21:24 ` William Morgan
2010-01-02 22:34 ` William Morgan
2010-01-03 15:18 ` William Morgan [this message]
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=1262531773-sup-5192@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