From: Jonathan Corbet <corbet@lwn.net>
To: frowand.list@gmail.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: submitting-patches - change non-ascii character to ascii
Date: Fri, 21 Jul 2017 11:27:25 -0600 [thread overview]
Message-ID: <20170721112725.45f5f580@lwn.net> (raw)
In-Reply-To: <1500600655-7938-1-git-send-email-frowand.list@gmail.com>
On Thu, 20 Jul 2017 18:30:55 -0700
frowand.list@gmail.com wrote:
> Documentation/process/submitting-patches.rst contains a non-ascii
> character. Change it to the ascii equivalent.
You should know better than to tell somebody like me that a hyphen and an
m-dash are equivalent! :)
I don't have any real objection to this change, but I am curious: is the
m-dash creating a problem somewhere? We have plenty of non-ASCII
characters in Documentation/ and beyond, why change this one? Or to put
it another way, do you think we should have an ASCII-only policy for
documentation files?
Thanks,
jon
next prev parent reply other threads:[~2017-07-21 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 1:30 [PATCH] docs: submitting-patches - change non-ascii character to ascii frowand.list
2017-07-21 17:27 ` Jonathan Corbet [this message]
2017-07-21 20:47 ` Frank Rowand
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=20170721112725.45f5f580@lwn.net \
--to=corbet@lwn.net \
--cc=frowand.list@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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