From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: ding@gnus.org
Subject: Re: Is QP bad for binary files?
Date: 11 Jul 2001 18:48:47 -0700 [thread overview]
Message-ID: <m17kxec3y8.fsf@halfdome.holdit.com> (raw)
In-Reply-To: <2nsng3lypc.fsf@piglet.jia.vnet>
>>>>> "ZSH" == ShengHuo ZHU <zsh@cs.rochester.edu> writes:
ZSH> I've changed the default to base64 instead of qp-or-base64.
Me too, because I was getting some PDFs that couldn't be encoded, and
it was very frustrating.
'(("text/x-patch" 8bit)
("text/.*" qp-or-base64)
("message/rfc822" 8bit)
("application/emacs-lisp" 8bit)
("application/x-patch" 8bit)
(".*" base64))
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
prev parent reply other threads:[~2001-07-12 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 23:00 Kai Großjohann
2001-07-12 1:27 ` Daniel Pittman
2001-07-12 1:31 ` ShengHuo ZHU
2001-07-12 1:48 ` Randal L. Schwartz [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=m17kxec3y8.fsf@halfdome.holdit.com \
--to=merlyn@stonehenge.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).