From: Andreas Schwab <schwab@linux-m68k.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH for 5.1] docs: fix trace docs build with sphinx 3.1.1
Date: Sun, 26 Jul 2020 22:49:11 +0200 [thread overview]
Message-ID: <87blk257eg.fsf@igel.home> (raw)
In-Reply-To: <20200714162659.1017432-1-berrange@redhat.com> ("Daniel P. Berrangé"'s message of "Tue, 14 Jul 2020 17:26:59 +0100")
On Jul 14 2020, Daniel P. Berrangé wrote:
> In Fedora 33 rawhide, we now have sphinx 3.1.1, as opposed
> to previous 2.2.2. This new version generates a warning on
> the source:
>
> docs/qemu-option-trace.rst.inc:4:Malformed option description
> '[enable=]PATTERN', should look like "opt", "-opt args",
> "--opt args", "/opt args" or "+opt args"
>
> This turns into an error when QEMU passes -W to sphinx-build
>
> Strangely the previous 2.2.2 code has the exact same logic
> for checking the syntax, but it is not being triggered. While
> it is only complaining about the first option, I changed all
> the options to give consistency.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Running Sphinx v1.7.6
[...]
Warning, treated as error:
../qemu-5.0.0/docs/qemu-option-trace.rst.inc:21:Duplicate explicit target name: "cmdoption-qemu-img-trace".
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-07-26 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 16:26 [PATCH for 5.1] docs: fix trace docs build with sphinx 3.1.1 Daniel P. Berrangé
2020-07-14 16:56 ` no-reply
2020-07-14 17:04 ` no-reply
2020-07-26 20:49 ` Andreas Schwab [this message]
2020-07-27 19:52 ` John Snow
2020-07-27 20:14 ` Peter Maydell
2020-07-28 23:40 ` John Snow
2020-07-29 10:37 ` Stefan Hajnoczi
2020-07-29 11:34 ` Daniel P. Berrangé
2020-07-29 14:55 ` Stefan Hajnoczi
2020-09-08 14:55 ` Laszlo Ersek
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=87blk257eg.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).