From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Jens Axboe <axboe@kernel.dk>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Documentation: kernel-doc: Promote "Writing kernel-doc comments" to page title
Date: Sun, 27 Mar 2022 12:27:20 +0700 [thread overview]
Message-ID: <49829de5-efe5-9065-d87a-2494d16b9465@gmail.com> (raw)
In-Reply-To: <20220326145332.0698a849@coco.lan>
On 26/03/22 20.56, Mauro Carvalho Chehab wrote:
> Hmm... I can't really see any differences... What this patch seems to be
> doing is to just change the markups for each level.
>
> See, on Sphinx, the first markup (whatever it is) is level 1, level 2
> the second different markup and so on.
>
> So, before this patch, kernel-doc.rst had:
>
> level 1: Writing kernel-doc comments
> =====================================
>
> level 2: How to format kernel-doc comments
> ------------------------------------------
>
> level 3: Function parameters
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> And after it, it will have:
>
> ====================================
> level 1: Writing kernel-doc comments
> ====================================
>
> level 2: How to format kernel-doc comments
> ==========================================
>
> level 3: Function parameters
> ----------------------------
>
> No semantic changes at all.
>
> The only (eventual) value of a change like that would be to make the
> levels more uniform, but IMO, it is not worth to apply a change like
> that, as:
>
> 1. There are a lot other documents that don't use the more commonly
> used level standard;
>
> 2. Making all .rst files to use the same definitions is hard;
>
> 3. Even if we place everything using identical markups for every
> level, as new stuff gets added, different (still valid)
> markups could be used on newer documents.
>
> Regards,
> Mauro
>
Indeed, fixing heading levels when adding title heading is required because
without it, Sphinx will complain "indentation inconsistency" error.
Maybe better splitting indentation level changes into its own patch, right?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-03-27 5:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 12:33 [PATCH v2 0/2] Documentation: doc-guide: Add missing page titles Bagas Sanjaya
2022-03-26 12:33 ` [PATCH v2 1/2] Documentation: kernel-doc: Promote "Writing kernel-doc comments" to page title Bagas Sanjaya
2022-03-26 13:56 ` Mauro Carvalho Chehab
2022-03-27 5:27 ` Bagas Sanjaya [this message]
2022-03-27 8:50 ` Akira Yokosawa
2022-03-26 12:33 ` [PATCH v2 2/2] Documentation: sphinx: replace "Introduction" chapter heading with " Bagas Sanjaya
2022-03-26 13:57 ` Mauro Carvalho Chehab
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=49829de5-efe5-9065-d87a-2494d16b9465@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akiyks@gmail.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=rafael.j.wysocki@intel.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).