Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
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] [PATCH] Decode messages according to their Content-Transfer-Encoding
Date: Fri, 04 Jun 2010 22:54:24 -0400	[thread overview]
Message-ID: <1275706048-sup-6981@zyrg.net> (raw)
In-Reply-To: <1275689764-sup-3384@midna.zekjur.net>

Excerpts from Michael Stapelberg's message of 2010-06-04 18:17:54 -0400:
>     Decode messages according to their Content-Transfer-Encoding
>         
>     This is necessary for MIME-messages (for example as part of multipart/signed)
>     which are encoded in base64.

Do we need to do this in other places too?
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2010-06-05  2: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 [this message]
2010-06-05 10:55   ` Michael Stapelberg
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=1275706048-sup-6981@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