Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] [PATCH] xapian: drop excessively long terms
Date: Wed, 05 Aug 2009 19:58:43 +0200	[thread overview]
Message-ID: <1249495000-sup-6057@ausone.home> (raw)
In-Reply-To: <1249493896-sup-7335@pion.club.cc.cmu.edu>

Excerpts from Rich Lane's message of Wed Aug 05 19:48:11 +0200 2009:
> Excerpts from Nicolas Pouillard's message of Wed Aug 05 13:29:48 -0400 2009:
> > I was planning to try a migration today, should I better wait a little?
> 
> I'd say go for it, just be aware you'll need to reindex soon. For the
> full experience compile svn xapian and export XAPIAN_PREFER_CHERT=1.

When you say the svn version you mean the trunk or the 1.0-branch ?

-- 
Nicolas Pouillard
http://nicolaspouillard.fr


  reply	other threads:[~2009-08-05 17:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-01 22:56 Rich Lane
2009-08-05 13:55 ` William Morgan
2009-08-05 14:54   ` Edward Z. Yang
2009-08-05 15:36   ` Rich Lane
2009-08-05 15:48     ` William Morgan
2009-08-05 17:29     ` Nicolas Pouillard
2009-08-05 17:48       ` Rich Lane
2009-08-05 17:58         ` Nicolas Pouillard [this message]
2009-08-05 18:06           ` Rich Lane

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=1249495000-sup-6057@ausone.home \
    --to=nicolas.pouillard@gmail.com \
    /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