From: Dmitry Paduchih <paduch@imm.uran.ru>
Subject: Re: (Patch) Cannot send unencoded text.
Date: 19 Apr 2001 22:52:56 +0600 [thread overview]
Message-ID: <87ae5c6dcn.fsf@ait.uran.ru> (raw)
In-Reply-To: <878zkx6o9h.fsf@ait.uran.ru> (Dmitry Paduchih's message of "19 Apr 2001 18:57:14 +0600")
Oops, please forgive me. I have found much simpler solution:
;;; Hm.
(add-to-list 'rfc2047-header-encoding-alist '("Subject" . none))
It simply wasn't documented. :)
>>>>> "DP" == Dmitry Paduchih <paduch@imm.uran.ru> writes:
DP> Hi,
DP> Here is a patch which is to allow sending messages with unencoded
DP> headers. I mean a possibility to do that, the defaults say to encode
DP> headers. I wrote in my yesterday letter the reasons why it is needed
DP> in my opinion. But it is only kinda work-arround.
DP> Seriously I think it is better to redesign the concept of
DP> message-options if I understand it correctly.
DP> Can somebody commit this patch?
DP> Thanks in advance,
DP> Dmitry
prev parent reply other threads:[~2001-04-19 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 9:31 error: " Dmitry Paduchih
2001-04-19 12:57 ` (Patch) " Dmitry Paduchih
2001-04-19 16:52 ` Dmitry Paduchih [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=87ae5c6dcn.fsf@ait.uran.ru \
--to=paduch@imm.uran.ru \
/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).