From: Randy Dunlap <rdunlap@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@infradead.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
corbet@lwn.net, jake@lwn.net, dchinner@redhat.com,
ritesh.list@gmail.com, rgoldwyn@suse.com, jack@suse.cz,
linux-doc@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
p.raghav@samsung.com, da.gomez@samsung.com,
rohan.puri@samsung.com
Subject: Re: [PATCH v2] Documentation: add initial iomap kdoc
Date: Mon, 22 May 2023 19:11:36 -0700 [thread overview]
Message-ID: <fb5c17bd-5e6a-ac68-8c6c-1bc67ed2af63@infradead.org> (raw)
In-Reply-To: <20230523012028.GE11598@frogsfrogsfrogs>
On 5/22/23 18:20, Darrick J. Wong wrote:
> On Thu, May 18, 2023 at 10:04:43PM -0700, Christoph Hellwig wrote:
>> On Thu, May 18, 2023 at 08:01:05AM -0700, Luis Chamberlain wrote:
>>> + Mapping of heading styles within this document:
>>> + Heading 1 uses "====" above and below
>>> + Heading 2 uses "===="
>>> + Heading 3 uses "----"
>>> + Heading 4 uses "````"
>>> + Heading 5 uses "^^^^"
>>> + Heading 6 uses "~~~~"
>>> + Heading 7 uses "...."
>>> +
>>> + Sections are manually numbered because apparently that's what everyone
>>
>> Why are you picking different defaults then the rest of the kernel
>> documentation?
>
> I bet Luis copied that from the online fsck document.
>
> IIRC the doc generator is smart enough to handle per-file heading usage.
> The rst parser sourcecode doesn't seem to have harcoded defaults; every
> time it sees an unfamiliar heading style in a .rst file, it adds that as
> the next level down in the hierarchy.
>
> Also, where are the "proper" headings documented for Documentation/?
Documentation/doc-guide/sphinx.rst:
* Please stick to this order of heading adornments:
and following lines.
--
~Randy
prev parent reply other threads:[~2023-05-23 2:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 15:01 [PATCH v2] Documentation: add initial iomap kdoc Luis Chamberlain
2023-05-18 15:49 ` Randy Dunlap
2023-05-18 20:55 ` Luis Chamberlain
2023-05-18 20:15 ` kernel test robot
2023-05-18 20:38 ` kernel test robot
2023-05-18 23:09 ` Jonathan Corbet
2023-05-19 1:48 ` Dave Chinner
2023-05-19 12:41 ` Jonathan Corbet
2023-05-19 5:04 ` Christoph Hellwig
2023-05-23 1:20 ` Darrick J. Wong
2023-05-23 2:11 ` Randy Dunlap [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=fb5c17bd-5e6a-ac68-8c6c-1bc67ed2af63@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=da.gomez@samsung.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jake@lwn.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=rgoldwyn@suse.com \
--cc=ritesh.list@gmail.com \
--cc=rohan.puri@samsung.com \
/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).