Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup exception
Date: Sat, 03 Jul 2010 09:35:38 -0400	[thread overview]
Message-ID: <1278164115-sup-7199@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1276137615-sup-4328@pinkfloyd.chass.utoronto.ca>

Excerpts from Ben Walton's message of Wed Jun 09 22:42:12 -0400 2010:

> I needed the following patch to run (old 1.8 here; no
> Symbol#to_proc).

Bump...

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

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-07-03 13:38 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
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 [this message]
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=1278164115-sup-7199@pinkfloyd.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --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