From: Akira Yokosawa <akiyks@gmail.com>
To: lukas.bulwahn@gmail.com
Cc: corbet@lwn.net, jani.nikula@intel.com,
kernel-janitors@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org,
workflows@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v2 3/3] docs: submit-checklist: change to autonumbered lists
Date: Thu, 29 Feb 2024 16:52:41 +0900 [thread overview]
Message-ID: <8df0c587-8f5b-4523-89d7-dc458ab2c1df@gmail.com> (raw)
In-Reply-To: <20240229030743.9125-4-lukas.bulwahn@gmail.com>
Hi Lukas,
I might be nitpicking too much, but let me go ahead...
On Thu, 29 Feb 2024 04:07:43 +0100, Lukas Bulwahn wrote:
> During review (see Link), Jani Nikula suggested to use autonumbered
> lists instead of manually-maintained bullet numbering.
>
> Turn all lists into autonumbered lists.
>
> Link: https://lore.kernel.org/linux-doc/87o7c3mlwb.fsf@intel.com/
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Documentation/process/submit-checklist.rst | 48 +++++++++++-----------
> 1 file changed, 24 insertions(+), 24 deletions(-)
>
> diff --git a/Documentation/process/submit-checklist.rst b/Documentation/process/submit-checklist.rst
> index e531dd504b6c..c984b747a755 100644
> --- a/Documentation/process/submit-checklist.rst
> +++ b/Documentation/process/submit-checklist.rst
> @@ -14,62 +14,62 @@ and elsewhere regarding submitting Linux kernel patches.
> Review your code
> ================
>
> -1) If you use a facility then #include the file that defines/declares
> +#. If you use a facility then #include the file that defines/declares
> that facility. Don't depend on other header files pulling in ones
> that you use.
Wait. This will render the list starting from:
1. If you use ...
In patch 1/1, you didn't change the ")".
It was Jani who suggested "#.", but "#)" would work just fine.
For details, see docutils' documentation at:
https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#enumerated-lists
By the way, you should be able to use auto enumeration in the 2nd-level
list as well.
> @@ -77,7 +77,7 @@ Check your code with tools
> Build your code
> ===============
>
> -1) Builds cleanly:
> +#. Builds cleanly:
>
> a) with applicable or modified ``CONFIG`` options ``=y``, ``=m``, and
> ``=n``. No ``gcc`` warnings/errors, no linker warnings/errors.
While the first item needs "a)", subsequent items can use "#)".
Either way,
Reviewed-by: Akira Yokosawa <akiyks@gmail.com>
Thanks, Akira
next prev parent reply other threads:[~2024-02-29 7:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 3:07 [PATCH v2 0/3] docs: submit-checklist: structure by category Lukas Bulwahn
2024-02-29 3:07 ` [PATCH v2 1/3] " Lukas Bulwahn
2024-02-29 3:07 ` [PATCH v2 2/3] docs: submit-checklist: use subheadings Lukas Bulwahn
2024-02-29 6:04 ` Randy Dunlap
2024-02-29 3:07 ` [PATCH v2 3/3] docs: submit-checklist: change to autonumbered lists Lukas Bulwahn
2024-02-29 6:06 ` Randy Dunlap
2024-02-29 7:52 ` Akira Yokosawa [this message]
2024-03-03 15:55 ` Jonathan Corbet
2024-03-03 18:19 ` Randy Dunlap
2024-03-04 1:14 ` Akira Yokosawa
2024-02-29 10:25 ` [PATCH v2 0/3] docs: submit-checklist: structure by category Jani Nikula
2024-02-29 10:36 ` Lukas Bulwahn
2024-03-03 16:00 ` Jonathan Corbet
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=8df0c587-8f5b-4523-89d7-dc458ab2c1df@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=rdunlap@infradead.org \
--cc=workflows@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