From: Ben Walton <bwalton@artsci.utoronto.ca>
To: Rich Lane <rlane@club.cc.cmu.edu>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH] Remove use of Object tap method
Date: Wed, 03 Mar 2010 13:25:04 -0500 [thread overview]
Message-ID: <1267640648-sup-2936@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1267639869-sup-1568@zyrg.net>
[-- Attachment #1.1: Type: text/plain, Size: 412 bytes --]
Excerpts from Rich Lane's message of Wed Mar 03 13:12:01 -0500 2010:
> What do you think about requiring the backports gem and getting rid of
> the compatibility code in util?
I wasn't aware of this gem. It sounds like a better route from the
supportability point of view. I'll check it out and see if there is
anything that isn't agreeable about it. Do others already have
experience with it?
Thanks
-Ben
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-03-03 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 19:20 Ben Walton
2010-03-02 22:10 ` rick.tessner
2010-03-02 22:46 ` Ben Walton
2010-03-03 18:12 ` Rich Lane
2010-03-03 18:25 ` Ben Walton [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=1267640648-sup-2936@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=rlane@club.cc.cmu.edu \
--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