From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Bad Subject folding (rfc2047) in 5.10.7
Date: Fri, 25 Mar 2005 18:22:17 +0900 [thread overview]
Message-ID: <b9yzmwsrsfq.fsf@jpl.org> (raw)
In-Reply-To: <v9psxo7sik.fsf@marauder.physik.uni-ulm.de>
Hi,
Please merge the changes I made in the v5-10 branch today into
the Emacs trunk. However, please don't bring back them into the
Gnus trunk because they are for only Gnus v5.11. The files which
I've changed in the v5-10 branch correspond to the following
ChangeLog entries:
2005-03-25 Katsumi Yamaoka <yamaoka@jpl.org>
* message.el
* mm-util.el
* rfc2047.el
2005-03-25 Lars Magne Ingebrigtsen <larsi@gnus.org>
Committed by Katsumi Yamaoka.
* rfc2047.el
2005-03-25 Jesper Harder <harder@ifa.au.dk>
Committed by Katsumi Yamaoka.
* rfc2047.el
2005-03-25 TSUCHIYA Masatoshi <tsuchiya@namazu.org>
Committed by Katsumi Yamaoka.
* rfc2047.el
2005-03-25 Katsumi Yamaoka <yamaoka@jpl.org>
* emacs-mime.texi
>>>>> In <v9psxo7sik.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:
> We already considered to sync `rfc2047.el' in the stable branch with
> the trunk version. I hope Katsumi Yamaoka will find to do it, see
> <http://thread.gmane.org/v93bvpyk3d.fsf%40marauder.physik.uni-ulm.de>.
Sorry I kept you waiting. emacs-w3m 1.4.4 has been released.
I sync'd rfc2047.el with the trunk as a starter. It has been
tested not only with recent Emacsen but also with Emacs 20.7 and
XEmacs 21.1.14. I will take a vacation next week and will start
the work on nnrss.el from the week after next (i.e., April 4).
Regards,
next prev parent reply other threads:[~2005-03-25 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3acoum8cs.fsf@obelix.wegge.dk>
2005-03-24 19:28 ` Bad Subject folding (rfc2047) in 5.10.7 (was: Wrapping header fields) Reiner Steib
2005-03-25 9:22 ` Katsumi Yamaoka [this message]
2005-03-25 9:59 ` Bad Subject folding (rfc2047) in 5.10.7 Miles Bader
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=b9yzmwsrsfq.fsf@jpl.org \
--to=yamaoka@jpl.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).