From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs-progs: fix documentation build errors
Date: Tue, 19 Nov 2024 14:56:14 +0800 [thread overview]
Message-ID: <cover.1731998908.git.anand.jain@oracle.com> (raw)
This patchset addresses documentation build issues related to
link formatting, indentation, and target name handling.
Anand Jain (3):
btrfs-progs: fix doc compile error in CHANGES file
btrfs-progs: fix doc build issue caused by confusion between BTRFS_
and target
btrfs-progs: fix doc build errors correct hyperlink formatting
CHANGES | 22 +++----
Documentation/Kernel-by-version.rst | 88 ++++++++++++++--------------
Documentation/dev/On-disk-format.rst | 2 +-
3 files changed, 56 insertions(+), 56 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-19 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 6:56 Anand Jain [this message]
2024-11-19 6:56 ` [PATCH 1/3] btrfs-progs: fix doc compile error in CHANGES file Anand Jain
2024-11-19 6:56 ` [PATCH 2/3] btrfs-progs: fix doc build issue caused by confusion between BTRFS_ and target Anand Jain
2024-11-19 6:56 ` [PATCH 3/3] btrfs-progs: fix doc build errors correct hyperlink formatting Anand Jain
2024-11-28 13:27 ` [PATCH 0/3] btrfs-progs: fix documentation build errors David Sterba
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=cover.1731998908.git.anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@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