From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: dsterba@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: fixup: v2 Documentation: placeholder for contents.rst file
Date: Thu, 11 Jan 2024 17:05:56 +0100 [thread overview]
Message-ID: <20240111160556.GI31555@twin.jikos.cz> (raw)
In-Reply-To: <adb208f0750fdbca06594f775eb0a81f886574c7.1704942814.git.anand.jain@oracle.com>
On Thu, Jan 11, 2024 at 12:21:00PM +0800, Anand Jain wrote:
> We don't need touch Documentation/contents.rst in the Makefile when
> Documentation/Makefile.in is doing it. Fix the devel commit 7479e750ba65
> ("btrfs-progs: docs: placeholder for contents.rst file on older sphinx version").
Thanks, I was not sure if the file should be in the toplevel directory
too. Updated in devel.
prev parent reply other threads:[~2024-01-11 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 17:25 [PATCH v2 0/2] btrfs-progs: Documentation: fix compile an error and Anand Jain
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 [this message]
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=20240111160556.GI31555@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=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