From: Eli Zaretskii <eliz@gnu.org>
To: Ken Olum <kdo@cosmos.phy.tufts.edu>
Cc: 28671-done@debbugs.gnu.org
Subject: bug#28671: 25.2; double transfer-encoding in rmailedit for complex mime messages
Date: Mon, 09 Oct 2017 16:55:55 +0300 [thread overview]
Message-ID: <83tvz8qvbo.fsf@gnu.org> (raw)
In-Reply-To: <q52bmlpxx07.fsf@cosmos.phy.tufts.edu> (message from Ken Olum on Mon, 02 Oct 2017 13:47:20 -0400)
> From: Ken Olum <kdo@cosmos.phy.tufts.edu>
> Cc: 28671@debbugs.gnu.org, kdo@cosmos.phy.tufts.edu
> Date: Mon, 02 Oct 2017 13:47:20 -0400
>
> Here is a test file. Edit the first message and make some change (e.g.,
> to the subject header). Then the body will end up base64 encoded
> twice. If you then go to the next message, the headers will have extra
> lines at the top due to marker problems. The patch should fix these
> problems.
>
> Here's a new patch with the simplified code as you suggested, and
> here's a change log entry:
Thanks, pushed to the release branch.
prev parent reply other threads:[~2017-10-09 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 15:37 bug#28671: 25.2; double transfer-encoding in rmailedit for complex mime messages Ken Olum
2017-10-02 16:37 ` Eli Zaretskii
2017-10-02 17:47 ` Ken Olum
2017-10-09 13:55 ` Eli Zaretskii [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tvz8qvbo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28671-done@debbugs.gnu.org \
--cc=kdo@cosmos.phy.tufts.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).