From: Rich Lane <rlane@club.cc.cmu.edu>
To: Michael Raitza <s2532038@inf.tu-dresden.de>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Added support for multiple sent sources.
Date: Sat, 27 Feb 2010 13:46:11 -0500 [thread overview]
Message-ID: <1267295844-sup-2000@zyrg.net> (raw)
In-Reply-To: <1265877393-sup-3156@leandros>
I don't see any backwards compatibility code for people who previously
used a different sent source.
I'm not sure there's much of a reason to have a number of SentManager
objects lightly wrapping a source. I'd just store the source directly.
I'd like to keep a tiny SentManager singleton around for its
default_source method.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-02-27 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 8:43 Michael Raitza
2010-02-27 18:46 ` Rich Lane [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=1267295844-sup-2000@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=s2532038@inf.tu-dresden.de \
--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