public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.com
Subject: [PATCH v2 0/2] btrfs-progs: Documentation: fix compile an error and
Date: Wed, 10 Jan 2024 22:55:21 +0530	[thread overview]
Message-ID: <cover.1704906806.git.anand.jain@oracle.com> (raw)


v2:
 Fix only the code-block:: without the argument and set it to none to
   match the rest of the code blocks.
 Use Documentation/Makefile.in to create the contents.rst file.
 Link to v1: https://lore.kernel.org/all/cover.1704438755.git.anand.jain@oracle.com/

Fixes a warning and an error during the build with Sphinx.

Anand Jain (2):
  btrfs-progs: Documentation: fix sphinx code-block warning
  btrfs-progs Documentation: placeholder for contents.rst file

 .gitignore                             |  1 +
 Documentation/Makefile.in              |  8 ++++++++
 Documentation/Tree-checker.rst         |  4 ++--
 Documentation/ch-subvolume-intro.rst   |  2 +-
 Documentation/dev/Developer-s-FAQ.rst  |  2 +-
 Documentation/dev/Experimental.rst     |  4 ++--
 Documentation/dev/dev-btrfs-design.rst |  8 ++++----
 Documentation/trouble-index.rst        | 16 ++++++++--------
 Makefile                               |  7 +++++++
 9 files changed, 34 insertions(+), 18 deletions(-)

-- 
2.31.1


             reply	other threads:[~2024-01-10 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 17:25 Anand Jain [this message]
2024-01-10 17:25 ` [PATCH v2 1/2] btrfs-progs: Documentation: fix sphinx code-block warning Anand Jain
2024-01-10 17:25 ` [PATCH v2 2/2] btrfs-progs Documentation: placeholder for contents.rst file Anand Jain
2024-01-10 21:52   ` David Sterba
2024-01-11  4:20     ` Anand Jain
2024-01-11  4:21 ` [PATCH] btrfs-progs: fixup: v2 " Anand Jain
2024-01-11 16:05   ` 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.1704906806.git.anand.jain@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.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