From: handa@gnu.org (K. Handa)
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 16286-done@debbugs.gnu.org
Subject: bug#16286: 24.3.50; insert-file-contents may bring invisible garbage
Date: Wed, 29 Jan 2014 22:40:51 +0900 [thread overview]
Message-ID: <87iot2ucrg.fsf@gnu.org> (raw)
In-Reply-To: <52E690DE.6070101@cs.ucla.edu> (message from Paul Eggert on Mon, 27 Jan 2014 09:01:18 -0800)
In article <52E690DE.6070101@cs.ucla.edu>, Paul Eggert <eggert@cs.ucla.edu> writes:
> Yes, thanks, that looks like a better patch.
Ok, I've just committed it.
---
Kenichi Handa
handa@gnu.org
prev parent reply other threads:[~2014-01-29 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 14:05 bug#16286: 24.3.50; insert-file-contents may bring invisible garbage Andrey Kotlarski
2014-01-02 16:30 ` Eli Zaretskii
2014-01-04 22:42 ` Andrey Kotlarski
2014-01-26 0:36 ` Paul Eggert
2014-01-27 15:01 ` K. Handa
2014-01-27 17:01 ` Paul Eggert
2014-01-29 13:40 ` K. Handa [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=87iot2ucrg.fsf@gnu.org \
--to=handa@gnu.org \
--cc=16286-done@debbugs.gnu.org \
--cc=eggert@cs.ucla.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).