From: Otto Sabart <ottosabart@seberm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Tejun Heo <tj@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] doc: cgroup: highlight all paths using the :file: inline markup
Date: Thu, 3 Jan 2019 13:34:56 +0100 [thread overview]
Message-ID: <20190103123456.GA7586@personal> (raw)
In-Reply-To: <20190102090948.1500a4a8@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On 02. Jan (Wednesday) v 09:09:48 -0700 2019, Jonathan Corbet wrote:
> On Wed, 2 Jan 2019 08:01:49 -0800
> Tejun Heo <tj@kernel.org> wrote:
>
> > On Sun, Dec 30, 2018 at 05:50:44PM +0100, Otto Sabart wrote:
> > > Improve readability using the :file: markup.
> >
> > Heh, that's a minor plus for formatted output and minor minus for the
> > source. If this is a convention generally followed for
> > documentations, I have no objects. That said, can you please reflow
> > the lines?
>
> The convention is to minimize markup, especially in cases where it's not
> really needed and it impairs the readability of the plain-text file. My
> feeling is that this particular markup doesn't provide enough benefit to
> be worth the cost.
>
> Otto, we all very much appreciate attempts to improve the documentation,
> and I hope you won't stop. If you would like to do RST work, one very
> helpful thing would be to look into the conversion of the (many) remaining
> plain-text documents and integration into the doc tree.
>
Hello Jon,
ok, I try to take a look into it.
Thank you,
Ota
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-01-03 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 16:50 [PATCH 2/2] doc: cgroup: highlight all paths using the :file: inline markup Otto Sabart
2019-01-02 16:01 ` Tejun Heo
2019-01-02 16:09 ` Jonathan Corbet
2019-01-03 12:34 ` Otto Sabart [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190103123456.GA7586@personal \
--to=ottosabart@seberm.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).