[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <26188ff7-9a0c-d72c-b956-63d8f1c500ba@gmail.com>
Date: Wed, 9 Nov 2022 15:28:54 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Akira Yokosawa <akiyks@...il.com>
Cc: corbet@....net, linux-kernel@...r.kernel.org,
linux-next@...r.kernel.org, paulmck@...nel.org, rcu@...r.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)
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
Powered by blists - more mailing lists