From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux ext4 <linux-ext4@vger.kernel.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jonathan Corbet <corbet@lwn.net>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/5] ext4 docs toctree reorganization
Date: Fri, 20 Jun 2025 17:56:39 +0700 [thread overview]
Message-ID: <20250620105643.25141-2-bagasdotme@gmail.com> (raw)
Hi Jon, hi Ted,
While discussing on my previous ext4 docs reorganization attempt
by merging contents [1], Jon suggested that considering current docs
file structure, a proper toctree would be ideal [2]. So, here's
the patchset that does exactly that.
Actual conversion to toctree structure is in [1/5], while the rest
is cleanups to make the resulting toctree nicer.
This patchset is based on docs-next tree.
Enjoy!
[1]: https://lore.kernel.org/linux-doc/20250618111544.22602-1-bagasdotme@gmail.com/
[2]: https://lore.kernel.org/linux-doc/87bjqjh5dr.fsf@trenco.lwn.net/
Bagas Sanjaya (5):
Documentation: ext4: Convert includes into toctrees
Documentation: ext4: Reduce toctree depth
Documentation: ext4: atomic_writes: Demote last three sections
Documentation: ext4: blockgroup: Add explicit title heading
Documentation: ext4: Move inode table short docs into its own file
.../filesystems/ext4/atomic_writes.rst | 10 ++++-----
Documentation/filesystems/ext4/bitmaps.rst | 7 ------
Documentation/filesystems/ext4/blockgroup.rst | 11 ++++++----
Documentation/filesystems/ext4/dynamic.rst | 10 +++++----
Documentation/filesystems/ext4/globals.rst | 15 ++++++++-----
Documentation/filesystems/ext4/index.rst | 2 +-
.../filesystems/ext4/inode_table.rst | 9 ++++++++
Documentation/filesystems/ext4/overview.rst | 22 ++++++++++---------
8 files changed, 49 insertions(+), 37 deletions(-)
create mode 100644 Documentation/filesystems/ext4/inode_table.rst
base-commit: d3f825032091fc14c7d5e34bcd54317ae4246903
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-06-20 10:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 10:56 Bagas Sanjaya [this message]
2025-06-20 10:56 ` [PATCH 1/5] Documentation: ext4: Convert includes into toctrees Bagas Sanjaya
2025-06-20 10:56 ` [PATCH 2/5] Documentation: ext4: Reduce toctree depth Bagas Sanjaya
2025-06-20 10:56 ` [PATCH 3/5] Documentation: ext4: atomic_writes: Demote last three sections Bagas Sanjaya
2025-06-20 10:56 ` [PATCH 4/5] Documentation: ext4: blockgroup: Add explicit title heading Bagas Sanjaya
2025-06-20 10:56 ` [PATCH 5/5] Documentation: ext4: Move inode table short docs into its own file Bagas Sanjaya
2025-06-30 0:53 ` [PATCH 0/5] ext4 docs toctree reorganization Bagas Sanjaya
2025-06-30 15:22 ` Darrick J. Wong
2025-07-01 19:11 ` Jonathan Corbet
2025-07-01 19:45 ` Darrick J. Wong
2025-07-01 19:52 ` Jonathan Corbet
2025-07-01 21:24 ` Theodore Ts'o
2025-07-02 22:59 ` 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=20250620105643.25141-2-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=corbet@lwn.net \
--cc=djwong@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
/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).