From: Rich Lane <rlane@club.cc.cmu.edu>
To: Brian May <brian@microcomaustralia.com.au>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup exception
Date: Wed, 09 Jun 2010 21:44:05 -0400 [thread overview]
Message-ID: <1276134110-sup-3620@zyrg.net> (raw)
In-Reply-To: <AANLkTikHlUdBtI5ZFd9H6WvUounPMn0BXyxyCdp1BHAD@mail.gmail.com>
I've pushed a workaround for this issue to master.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-06-10 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 1:08 Brian May
2010-06-10 0:39 ` Brian May
2010-06-10 1:44 ` Rich Lane [this message]
2010-06-10 2:00 ` Brian May
2010-06-10 2:15 ` Rich Lane
2010-06-10 2:42 ` Ben Walton
2010-07-03 13:35 ` Ben Walton
2010-07-13 2:05 ` Rich Lane
2010-06-10 2:47 ` Brian May
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=1276134110-sup-3620@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=brian@microcomaustralia.com.au \
--cc=sup-talk@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