All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Luca Boccassi <bluca@debian.org>,
	 Bruce Richardson <bruce.richardson@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	 Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [PATCH] doc: rebuild all Sphinx guides
Date: Tue, 7 Feb 2023 09:54:32 +0100	[thread overview]
Message-ID: <CAJFAV8wzVjo0UTHpj2opDBESH4N0P7o6mCJZqGFpeAu5CY2q=A@mail.gmail.com> (raw)
In-Reply-To: <20230207084352.3325416-1-thomas@monjalon.net>

On Tue, Feb 7, 2023 at 9:44 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> On some systems, Sphinx is lazy enough to not recompile an RST file,
> even if it contains a link pointing to a file which has been removed.
>
> In order to detect such broken links,
> the option "-a" is used to always rebuild all.

I can't reproduce such behavior, but the principle looks ok to me and
I did not notice a difference in terms of time spending generating the
documentation.

>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>

We have no guide describing Sphinx, I'd rather update this patch title
like "doc: rebuild all guides with Sphinx".
Reviewed-by: David Marchand <david.marchand@redhat.com>


-- 
David Marchand


  reply	other threads:[~2023-02-07  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07  8:43 [PATCH] doc: rebuild all Sphinx guides Thomas Monjalon
2023-02-07  8:54 ` David Marchand [this message]
2023-02-07  9:09   ` Thomas Monjalon
2023-02-14 11:31     ` Thomas Monjalon

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='CAJFAV8wzVjo0UTHpj2opDBESH4N0P7o6mCJZqGFpeAu5CY2q=A@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=thomas@monjalon.net \
    /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.