linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH v2 0/2] Documentation: doc-guide: Add missing page titles
Date: Sat, 26 Mar 2022 19:33:36 +0700	[thread overview]
Message-ID: <20220326123337.642536-1-bagasdotme@gmail.com> (raw)

Add missing page title for
Documentation/doc-guide/{kernel-doc,sphinx}.rst. Without it, top-level
TOC for doc-guide directly shows chapter headings instead.

Changes since v1 [1]:
  - Split into two patches
  - Promote "Writing kernel-doc comments" (suggested by Jonathan
    Corbet)
  - Use suggested page title from Jonathan Corbet for sphinx.rst

[1]: https://lore.kernel.org/linux-doc/20220322113645.502544-1-bagasdotme@gmail.com/

Bagas Sanjaya (2):
  Documentation: kernel-doc: Promote "Writing kernel-doc comments" to
    page title
  Documentation: sphinx: replace "Introduction" chapter heading with
    page title

 Documentation/doc-guide/kernel-doc.rst | 29 +++++++++++++-------------
 Documentation/doc-guide/sphinx.rst     |  5 +++--
 2 files changed, 18 insertions(+), 16 deletions(-)


base-commit: f443e374ae131c168a065ea1748feac6b2e76613
-- 
An old man doll... just what I always wanted! - Clara


             reply	other threads:[~2022-03-26 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26 12:33 Bagas Sanjaya [this message]
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
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=20220326123337.642536-1-bagasdotme@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=linux-doc@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;
as well as URLs for NNTP newsgroup(s).