From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] mail gem no longer needs activesupport [was: sup-server revisited]
Date: Tue, 10 May 2011 12:06:08 +0000 [thread overview]
Message-ID: <1305029054-sup-718@masanjin.net> (raw)
In-Reply-To: <1304872142-sup-6096@whisper>
Reformatted excerpts from Hamish's message of 2011-05-08:
> Might be a bit late, but I've just noticed that they're taking the
> activesupport dependency out, as of mail 2.3.0
Good to know. I won't switch Heliotrope over just for the heck of it,
but if I encounter insurmountable problems with RubyMail we'll at least
have a backup plan.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2011-05-10 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 16:36 Hamish
2011-05-10 12:06 ` William Morgan [this message]
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=1305029054-sup-718@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@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