From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux bcachefs <linux-bcachefs@vger.kernel.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Jonathan Corbet <corbet@lwn.net>, Wei Liu <wei.liu@kernel.org>,
Easwar Hariharan <eahariha@linux.microsoft.com>,
Michael Kelley <mhklinux@outlook.com>,
Purva Yeshi <purvayeshi550@gmail.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/3] bcachefs: docs index refactoring
Date: Mon, 24 Feb 2025 19:40:25 +0700 [thread overview]
Message-ID: <20250224124028.42059-1-bagasdotme@gmail.com> (raw)
Hi Kent,
Here is bcachefs docs toctree reorganizing (inspired by similar work on
tracing subsystem by Purva Yeshi [Cc'ed] [1]). The actual refactoring
is in patches [1/3] and [2/3]. Patch [3/3] is a bonus: footnotes
formatting.
Enjoy!
[1]: https://lore.kernel.org/linux-doc/20250217110637.6640-1-purvayeshi550@gmail.com/
Bagas Sanjaya (3):
Documentation: bcachefs: Split index toctree
Documentation: bcachefs: SubmittingPatches: Demote section headings
Documentation: bcachefs: SubmittingPatches: Convert footnotes to reST
syntax
.../bcachefs/SubmittingPatches.rst | 43 +++++++++++--------
Documentation/filesystems/bcachefs/index.rst | 19 +++++++-
2 files changed, 43 insertions(+), 19 deletions(-)
base-commit: d139df3ad938bd1e18bcc16c2452dea1cf852807
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-02-24 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 12:40 Bagas Sanjaya [this message]
2025-02-24 12:40 ` [PATCH 1/3] Documentation: bcachefs: Split index toctree Bagas Sanjaya
2025-02-24 12:40 ` [PATCH 2/3] Documentation: bcachefs: SubmittingPatches: Demote section headings Bagas Sanjaya
2025-02-24 12:40 ` [PATCH 3/3] Documentation: bcachefs: SubmittingPatches: Convert footnotes to reST syntax Bagas Sanjaya
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=20250224124028.42059-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=eahariha@linux.microsoft.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=purvayeshi550@gmail.com \
--cc=wei.liu@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
all inboxes | Powered by JetHome®