Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] sources.yaml labels
Date: Sun, 06 Sep 2009 10:07:55 -0400	[thread overview]
Message-ID: <1252246006-sup-3945@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1252242820-sup-1452@masanjin.net>

Excerpts from William Morgan's message of Sun Sep 06 09:22:21 -0400 2009:

> The other source of bad labels is the serialized version of the messages
> stored by Xapian, if you use Xapian. But if you've regenerated your
> Xapian index recently, this shouldn't be a problem...

Since I had a bad hook and imported to Xapian with that hook live,
should I reimport my dumpfile after having the hook removed?  I'm
thinking that I did the damage in a permanent fashion while doing the
import...

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090906/e357aff1/attachment.bin>


  parent reply	other threads:[~2009-09-06 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-06  0:19 Ben Walton
2009-09-06 13:22 ` William Morgan
2009-09-06 13:47   ` Ben Walton
2009-09-06 14:16     ` Ingmar Vanhassel
2009-09-06 14:07   ` Ben Walton [this message]
2009-09-06 15:06     ` William Morgan
2009-09-06 15:26       ` Ben Walton
2009-09-06 16:41       ` Ben Walton

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=1252246006-sup-3945@ntdws12.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    /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