From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sources.yaml labels
Date: Sun, 06 Sep 2009 08:06:16 -0700 [thread overview]
Message-ID: <1252248461-sup-5213@masanjin.net> (raw)
In-Reply-To: <1252246006-sup-3945@ntdws12.chass.utoronto.ca>
Reformatted excerpts from Ben Walton's message of 2009-09-06:
> 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...
I suspect that would fix it. I've just pushed a change to to make
Message#add_label coerce arguments to symbols, anyways, so that writing
your hook wrong won't destroy your index for all eternity.
Sorry about all this. The silver lining is that it's a side effect of
lots of development activity. :)
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-09-06 15:06 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
2009-09-06 15:06 ` William Morgan [this message]
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=1252248461-sup-5213@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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