From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Thorsten Leemhuis <linux@leemhuis.info>,
Kees Cook <keescook@chromium.org>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v2 7/7] docs: put atomic*.txt and memory-barriers.txt into the core-api book
Date: Sun, 25 Sep 2022 10:18:01 +0700 [thread overview]
Message-ID: <e97ff5c9-6ffb-08b0-0da0-8035fe2dc877@gmail.com> (raw)
In-Reply-To: <87a66qp5vn.fsf@meer.lwn.net>
On 9/23/22 20:39, Jonathan Corbet wrote:
>> Shouldn't warning like "This documentation isn't in RST format and included
>> as literal block" be added?
>
> Why? Who needs that information and what will they do with it?
At least readers will not be surprised with the anomaly...
But anyway, for consistency, I'd like to see these *.txt docs be converted
to proper RST.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-09-25 3:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:41 [PATCH v2 0/4] Rewrite the top-level index.rst Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 1/7] docs: promote the title of process/index.html Jonathan Corbet
2022-09-23 17:53 ` David Vernet
2022-09-23 18:31 ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 2/7] docs: Rewrite the front page Jonathan Corbet
2022-09-23 19:02 ` Randy Dunlap
2022-09-23 19:07 ` Jonathan Corbet
2022-09-24 2:05 ` David Vernet
2022-09-22 20:41 ` [PATCH v2 3/7] docs: reconfigure the HTML left column Jonathan Corbet
2022-09-24 2:13 ` David Vernet
2022-09-22 20:41 ` [PATCH v2 4/7] docs: remove some index.rst cruft Jonathan Corbet
2022-09-24 2:14 ` David Vernet
2022-09-22 20:41 ` [PATCH v2 5/7] docs: move asm-annotations.rst into core-api Jonathan Corbet
2022-09-23 7:45 ` Bagas Sanjaya
2022-09-24 2:10 ` kernel test robot
2022-09-24 2:20 ` David Vernet
2022-09-25 3:54 ` Bagas Sanjaya
2022-09-25 21:29 ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 6/7] docs: Expand the front-page CPU-architecture section Jonathan Corbet
2022-09-24 2:25 ` David Vernet
2022-09-25 21:50 ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 7/7] docs: put atomic*.txt and memory-barriers.txt into the core-api book Jonathan Corbet
2022-09-23 4:25 ` Bagas Sanjaya
2022-09-23 13:39 ` Jonathan Corbet
2022-09-25 3:18 ` Bagas Sanjaya [this message]
2022-09-25 3:48 ` Randy Dunlap
2022-09-25 3:52 ` Bagas Sanjaya
2022-09-23 18:44 ` Randy Dunlap
2022-09-23 19:06 ` Jonathan Corbet
2022-09-23 8:09 ` [PATCH v2 0/4] Rewrite the top-level index.rst Jani Nikula
2022-09-23 8:55 ` Thorsten Leemhuis
2022-09-23 13:45 ` Jonathan Corbet
2022-09-23 14:43 ` Thorsten Leemhuis
2022-09-23 15:03 ` Jonathan Corbet
2022-09-23 17:45 ` Kees Cook
2022-09-24 1:56 ` David Vernet
2022-09-23 18:48 ` Randy Dunlap
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=e97ff5c9-6ffb-08b0-0da0-8035fe2dc877@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
/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).