From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] sources.yaml labels
Date: Sun, 06 Sep 2009 11:26:26 -0400 [thread overview]
Message-ID: <1252250590-sup-9666@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1252248461-sup-5213@masanjin.net>
Excerpts from William Morgan's message of Sun Sep 06 11:06:16 -0400 2009:
> 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.
Ok, that's cool. I was going to write the same change but with a
'raise ArgumentError' similar to the one in << to stick with the fail
fast approach you prefer.
> Sorry about all this. The silver lining is that it's a side effect of
> lots of development activity. :)
Hey, it's not a problem. I don't mind guinea pigging this stuff at
all. Sup has steadily improved since I've been using it, so I'm a
happy camper. [Plus, I'm running next, so I 'get what I get.']
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/26890640/attachment.bin>
next prev parent reply other threads:[~2009-09-06 15:26 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
2009-09-06 15:26 ` Ben Walton [this message]
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=1252250590-sup-9666@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