From: Rich Lane <rlane@club.cc.cmu.edu>
To: Michael Stapelberg <michael+sup@stapelberg.de>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] RubyMail cannot handle multipart/signed messages
Date: Tue, 20 Apr 2010 11:27:54 -0400 [thread overview]
Message-ID: <1271776749-sup-2472@zyrg.net> (raw)
In-Reply-To: <1271745597-sup-8192@midna.zekjur.net>
Excerpts from Michael Stapelberg's message of 2010-04-20 02:40:36 -0400:
> So, when do we switch to 'mail'?
I'm all for it but we need to be careful about regressions. We'd need
to have a pretty extensive testsuite covering Message and Chunk before
switching, which is a bigger effort than the switch itself.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-04-20 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 7:43 Michael Stapelberg
2010-04-19 12:55 ` Sam Hall
2010-04-19 15:57 ` Michael Stapelberg
2010-04-20 6:26 ` Sam Hall
2010-04-20 6:40 ` Michael Stapelberg
2010-04-20 15:27 ` 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=1271776749-sup-2472@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=michael+sup@stapelberg.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