From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
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, 07 Feb 2023 10:09:20 +0100 [thread overview]
Message-ID: <2628508.q0ZmV6gNhb@thomas> (raw)
In-Reply-To: <CAJFAV8wzVjo0UTHpj2opDBESH4N0P7o6mCJZqGFpeAu5CY2q=A@mail.gmail.com>
07/02/2023 09:54, David Marchand:
> 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.
I think your system behaves with -a option forced somewhere.
> > 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".
Yes
> Reviewed-by: David Marchand <david.marchand@redhat.com>
next prev parent reply other threads:[~2023-02-07 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 8:43 Thomas Monjalon
2023-02-07 8:54 ` David Marchand
2023-02-07 9:09 ` Thomas Monjalon [this message]
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=2628508.q0ZmV6gNhb@thomas \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=maxime.coquelin@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).