From: Peter Maydell <peter.maydell@linaro.org>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Lukas Straub <lukasstraub2@web.de>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 00/10] For 6.0 patches
Date: Tue, 30 Mar 2021 12:11:30 +0000 [thread overview]
Message-ID: <CAFEAcA8dnsC30ZQVXOCLWdwb50nQFcWQjRZB_m5S6Mpv3WC2Ug@mail.gmail.com> (raw)
In-Reply-To: <CAJ+F1CK2jf5O226zLqpKt_=9mSE4t979huMZ0s9FGZ4TATKguA@mail.gmail.com>
On Tue, 30 Mar 2021 at 09:29, Marc-André Lureau
<marcandre.lureau@gmail.com> wrote:
>
> Hi
>
> On Mon, Mar 29, 2021 at 9:54 PM Peter Maydell <peter.maydell@linaro.org> wrote:
>> aarch64 CI machine, which has python 3.8.5 and sphinx-build 1.8.5.
>> My guess is that it might be the sphinx-build version here. I vaguely
>> recall that Sphinx is kind of picky about exceptions within the conf
>> file but that there was a change in what it allowed at some point.
>> It's possible we just can't do much with the old versions.
>
>
> How do you run the build? Running make from an existing configured or build state? If so, I have seen sphinx errors that don't stop the build (and actually building the docs without sphinx-rtd). I don't know why this happens, "regenerate"/reconfigure errors should stop the build.
On that machine, yes, it's an incremental build.
thanks
-- PMM
next prev parent reply other threads:[~2021-03-30 12:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 18:45 [PULL 00/10] For 6.0 patches marcandre.lureau
2021-03-28 18:45 ` [PULL 01/10] util: fix use-after-free in module_load_one marcandre.lureau
2021-03-28 18:45 ` [PULL 02/10] dbus-vmstate: Increase the size of input stream buffer used during load marcandre.lureau
2021-03-28 18:45 ` [PULL 03/10] sphinx: adopt kernel readthedoc theme marcandre.lureau
2021-03-28 18:45 ` [PULL 04/10] docs: simplify each section title marcandre.lureau
2021-03-28 18:45 ` [PULL 05/10] yank: Remove dependency on qiochannel marcandre.lureau
2021-03-28 18:45 ` [PULL 06/10] yank: Always link full yank code marcandre.lureau
2021-03-28 18:45 ` [PULL 07/10] chardev/char.c: Move object_property_try_add_child out of chardev_new marcandre.lureau
2021-03-28 18:45 ` [PULL 08/10] chardev/char.c: Always pass id to chardev_new marcandre.lureau
2021-03-28 18:45 ` [PULL 09/10] chardev: Fix yank with the chardev-change case marcandre.lureau
2021-03-28 18:45 ` [PULL 10/10] tests: Add tests for " marcandre.lureau
2021-03-28 19:00 ` [PULL 00/10] For 6.0 patches no-reply
2021-03-29 13:53 ` Peter Maydell
2021-03-29 14:16 ` Marc-André Lureau
2021-03-29 15:56 ` Peter Maydell
2021-03-29 16:30 ` Marc-André Lureau
2021-03-29 17:54 ` Peter Maydell
2021-03-30 8:29 ` Marc-André Lureau
2021-03-30 12:11 ` Peter Maydell [this message]
2021-03-30 14:36 ` Marc-André Lureau
2021-03-29 16:26 ` Lukas Straub
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=CAFEAcA8dnsC30ZQVXOCLWdwb50nQFcWQjRZB_m5S6Mpv3WC2Ug@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=lukasstraub2@web.de \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.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.