From: Michael Stapelberg <michael+sup@stapelberg.de>
To: Rich Lane <rlane@club.cc.cmu.edu>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Decode messages according to their Content-Transfer-Encoding
Date: Sat, 05 Jun 2010 12:55:39 +0200 [thread overview]
Message-ID: <1275735302-sup-799@midna.zekjur.net> (raw)
In-Reply-To: <1275706048-sup-6981@zyrg.net>
Hi Rich,
Excerpts from Rich Lane's message of 2010-06-05 04:54:24 +0200:
> Do we need to do this in other places too?
Not sure, unfortunately. I’d guess only for MIME messages, for other
messages the Transfer-Encoding seems to work already.
Best regards,
Michael
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-06-05 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 22:17 Michael Stapelberg
2010-06-05 2:54 ` Rich Lane
2010-06-05 10:55 ` Michael Stapelberg [this message]
2010-06-07 15:55 ` Rich Lane
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=1275735302-sup-799@midna.zekjur.net \
--to=michael+sup@stapelberg.de \
--cc=rlane@club.cc.cmu.edu \
--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