From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 27141@debbugs.gnu.org, yamaoka@jpl.org
Subject: bug#27141: 26.0.50; mml-generate-mime-1 broken
Date: Wed, 13 Sep 2017 21:41:30 +0300 [thread overview]
Message-ID: <83k212o2zp.fsf@gnu.org> (raw)
In-Reply-To: <87fubqzej4.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Wed, 13 Sep 2017 19:36:47 +0200)
unblock 24655 by 27141
thanks
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, 27141@debbugs.gnu.org
> Date: Wed, 13 Sep 2017 19:36:47 +0200
>
> I seem to have forgotten to tag my patch with the corresponding bug
> report? Annoying. Anyway, the problem my patch fixed was dealing with
> text files included in Message with mml tags -- they would (under some
> circumstances; there was a test case in the original bug report) be
> corrupted.
>
> But my fix was obviously a mistake, since it resulted in pretty much all
> multibyte buffers being mishandled when forwarding, so the original
> problem will have to be fixed in a different way.
>
> But I don't think this should be a release blocker.
Thanks, I'm unblocking it. Though I hope this will be fixed before
26.1 is out.
next prev parent reply other threads:[~2017-09-13 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 6:09 bug#27141: 26.0.50; mml-generate-mime-1 broken Katsumi Yamaoka
2017-05-31 23:21 ` Katsumi Yamaoka
2017-06-01 5:20 ` Lars Ingebrigtsen
2017-06-01 6:15 ` Katsumi Yamaoka
2017-06-01 7:17 ` Lars Ingebrigtsen
2017-06-01 8:32 ` Katsumi Yamaoka
2017-09-02 14:05 ` Eli Zaretskii
2017-09-03 23:37 ` Katsumi Yamaoka
2017-09-13 17:36 ` Lars Ingebrigtsen
2017-09-13 18:41 ` Eli Zaretskii [this message]
2017-09-13 18:45 ` Lars Ingebrigtsen
2017-09-13 19:14 ` Eli Zaretskii
2017-09-13 19:18 ` Lars Ingebrigtsen
2019-09-23 18:15 ` Lars Ingebrigtsen
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=83k212o2zp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27141@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=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.
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).