From: Tino Calancha <tino.calancha@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: 23867@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#23867: 25.1.50; Doc string containing `\N'
Date: Wed, 29 Jun 2016 19:01:09 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1606291900130.1391@calancha-pc> (raw)
In-Reply-To: <mvmwpl8gw50.fsf@hawking.suse.de>
On Wed, 29 Jun 2016, Andreas Schwab wrote:
> Before that "\N" was the same as "N", so there is no point in writing
> that.
Good point. Thank you.
Tino
next prev parent reply other threads:[~2016-06-29 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 9:44 bug#23867: 25.1.50; Doc string containing `\N' Tino Calancha
2016-06-29 9:52 ` Andreas Schwab
2016-06-29 10:01 ` Tino Calancha [this message]
2016-06-29 14:00 ` Drew Adams
2016-06-29 14:15 ` Andreas Schwab
2016-06-29 14:44 ` Noam Postavsky
2016-07-04 16:43 ` Glenn Morris
2016-07-06 14:56 ` Paul Eggert
2016-07-06 15:35 ` Glenn Morris
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=alpine.DEB.2.20.1606291900130.1391@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=23867@debbugs.gnu.org \
--cc=schwab@suse.de \
/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).