All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] btrfs-progs Documentation: placeholder for contents.rst file
Date: Wed, 10 Jan 2024 01:47:52 +0100	[thread overview]
Message-ID: <20240110004752.GL28693@suse.cz> (raw)
In-Reply-To: <542615e6-fad2-3469-f173-f761e33880a6@oracle.com>

On Wed, Jan 10, 2024 at 06:06:11AM +0530, Anand Jain wrote:
> >>>> ---
> >>>> RFC because the empty contents.rst to fix the error.
> >>>
> >>> Adding an empty file to silence the error is probably ok but what's the
> >>> reason to have it?
> >>
> >> While contents.rst similar to index.rst with its Table of Contents
> >> (TOC) and toctree directives. But, I am not sure yet if we can replace
> >> index.rst with contents.rst. And doing it ended up with multiple errors.
> >> So, I abandoned the idea, restored to creating an empty file instead.
> >> It appears that contents.rst is needed only in older versions like'
> >> 1.7.6.
> > 
> > Ok then, the empty file would be a fix but it leads to this warning on a
> > newer version:
> > 
> > .../contents.rst: WARNING: document isn't included in any toctree
> > 
> > We could add it conditionally at build time in case the sphinx version
> > is old, with something like that:
> > 
> > .PHONY: contents.rst
> > 
> > contents.rst:
> > 	if "sphinx --version < 3.2.1"; then touch contents.rst; fi
> 
> Ah. Thanks let me try.
> 
> Also, I am testing it manually using man, is there anything I am missing?

I think not, the manual pages are default build target, although you can
also try 'make html' if it's without warnings.

      reply	other threads:[~2024-01-10  0:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08  8:31 [PATCH 0/2] btrfs-progs: Documentation: fix compile an error and Anand Jain
2024-01-08  8:31 ` [PATCH 1/2] btrfs-progs: Documentation: fix sphinx code-block warning Anand Jain
2024-01-09 16:19   ` David Sterba
2024-01-10  0:34     ` Anand Jain
2024-01-08  8:31 ` [PATCH RFC 2/2] btrfs-progs Documentation: placeholder for contents.rst file Anand Jain
2024-01-08 21:33   ` David Sterba
2024-01-09 13:25     ` Anand Jain
2024-01-09 16:23       ` David Sterba
2024-01-10  0:36         ` Anand Jain
2024-01-10  0:47           ` 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=20240110004752.GL28693@suse.cz \
    --to=dsterba@suse.cz \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.