From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [sup-talk] Ferret to Xapian conversion
Date: Sun, 03 Jan 2010 14:07:16 -0800 [thread overview]
Message-ID: <1262556388-sup-4595@masanjin.net> (raw)
In-Reply-To: <1262546960-sup-6875@home.mrtheplague.net>
Reformatted excerpts from Anthony Martinez's message of 2010-01-03:
> Here is a patch to make it complain about not having Xapian *before* starting
> the state dump, so it doesn't get to step 3 and suddenly find out that it can't
> load Xapian.
Added to ferret-deprecation with minor editing, and remerged into next.
Thanks!
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-01-03 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1262460996-sup-1383@home.mrtheplague.net>
[not found] ` <1262467343-sup-9565@masanjin.net>
[not found] ` <1262471675-sup-1708@masanjin.net>
[not found] ` <1262531773-sup-5192@masanjin.net>
2010-01-03 19:38 ` Anthony Martinez
2010-01-03 20:18 ` Rich Lane
2010-01-03 22:47 ` Anthony Martinez
2010-01-03 22:07 ` 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=1262556388-sup-4595@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@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