From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: corbet@lwn.net, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, paulmck@kernel.org,
rcu@vger.kernel.org
Subject: Re: [PATCH] Documentation: RCU: use code blocks with autogenerated line (was: Re: linux-next: build warning after merge of the rcu tree)
Date: Wed, 9 Nov 2022 15:28:54 +0700 [thread overview]
Message-ID: <26188ff7-9a0c-d72c-b956-63d8f1c500ba@gmail.com> (raw)
In-Reply-To: <fd1903d4-a721-931e-c928-1818cd650490@gmail.com>
On 11/8/22 21:53, Akira Yokosawa wrote:
>> I think only rcubarrier.rst have explicit references to line numbers.
>
> Oh, I find such references in (not limited to):
>
> - Documentation/RCU/Design/Requirements/Requirements.rst
> - Documentation/RCU/Design/Data-Structures/Data-Structures.rst
>
Ah, I don't see these above!
> Remember there is a note in Documentation/doc-guide/sphinx.rst
> which reads:
>
> Please don't go overboard with reStructuredText markup. Keep it simple.
> For the most part the documentation should be plain text with just enough
> consistency in formatting that it can be converted to other formats.
>
> My interpretation of above:
>
> .rst sources should be kept as close to plain-text which can be
> easily understood in dumb terminals, as far as possible.
>
Ah! I always forget that. I'm leaning towards *abusing* the markup,
though.
Thanks for the reminder.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2022-11-09 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 3:26 linux-next: build warning after merge of the rcu tree Stephen Rothwell
2022-11-07 5:02 ` Paul E. McKenney
2022-11-07 9:55 ` [PATCH] Documentation: RCU: use code blocks with autogenerated line (was: Re: linux-next: build warning after merge of the rcu tree) Bagas Sanjaya
2022-11-07 11:48 ` Akira Yokosawa
2022-11-07 17:50 ` Paul E. McKenney
2022-11-08 2:29 ` Bagas Sanjaya
2022-11-08 14:53 ` Akira Yokosawa
2022-11-09 8:28 ` Bagas Sanjaya [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=26188ff7-9a0c-d72c-b956-63d8f1c500ba@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@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