From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Kitt <steve@sk2.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: format kernel-parameters -- as code
Date: Fri, 28 Jun 2019 12:48:04 -0600 [thread overview]
Message-ID: <20190628124804.5ce44f04@lwn.net> (raw)
In-Reply-To: <20190628203841.723ccd9c@heffalump.sk2.org>
On Fri, 28 Jun 2019 20:38:41 +0200
Stephen Kitt <steve@sk2.org> wrote:
> Right, looking further shows a large number of places where -- is handled
> incorrectly. The following patch disables this “smart” handling wholesale;
> I’ll follow up (in the next few days) with patches to use real em- and
> en-dashes where appropriate.
Thanks for figuring that out, it seems like the right thing to do.
Let's not worry about "real" dashes for now. Not everybody welcomes
non-ascii characters in the docs and, for dashes, it's something I deemed
not worth fighting about.
Thanks,
jon
next prev parent reply other threads:[~2019-06-28 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 13:59 [PATCH] docs: format kernel-parameters -- as code Stephen Kitt
2019-06-28 15:10 ` Jonathan Corbet
2019-06-28 18:38 ` Stephen Kitt
2019-06-28 18:48 ` Jonathan Corbet [this message]
2019-06-28 20:47 ` Randy Dunlap
2019-06-28 20:51 ` Stephen Kitt
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=20190628124804.5ce44f04@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@sk2.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.