From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] new mail library
Date: Wed, 04 Aug 2010 15:50:45 -0400 [thread overview]
Message-ID: <1280951408-sup-6399@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1280949385.17490.59.camel@raker.ateb.com>
Excerpts from Reid Thompson's message of Wed Aug 04 15:16:25 -0400 2010:
> but it is listed in the gemspec
> s.add_dependency('activesupport', ">= 2.3.6")
...and was definitely pulled in when I installed the gem. As I said,
it's more heavy weight, but it is very nice to use so far.
-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
next prev parent reply other threads:[~2010-08-04 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 1:47 Ben Walton
2010-08-04 18:20 ` William Morgan
2010-08-04 19:11 ` Reid Thompson
2010-08-04 19:16 ` Reid Thompson
2010-08-04 19:50 ` Ben Walton [this message]
2010-08-04 20:01 ` Anthony Martinez
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=1280951408-sup-6399@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