From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [PATCH v2 0/3] docs: fix and cleanup footnotes
Date: Fri, 11 Oct 2024 13:12:46 +0200 [thread overview]
Message-ID: <20241011111249.47530-1-pbonzini@redhat.com> (raw)
Sphinx 8.1.0 got a lot better at detecting unreferenced footnotes, and
we have three of them---which causes the build to fail when the latest
version of sphinx is installed from Pip.
Patches 1 and 2 fix them, while the third is a general improvement in
the appearance of the rendered footnotes and the consistency of the
rST syntax.
An example of a failing job is https://gitlab.com/bonzini/qemu/-/jobs/8060240732.
Paolo
v1->v2: improve commit messages
replace patch 2, absorbing the rapl-msr.rst changes into it
Paolo Bonzini (3):
docs: fix invalid footnote syntax
docs: avoid footnotes consisting of just URLs
docs: use consistent markup for footnotes
docs/devel/atomics.rst | 6 +++---
docs/devel/build-system.rst | 6 +++---
docs/devel/loads-stores.rst | 2 +-
docs/devel/maintainers.rst | 4 ++--
docs/devel/migration/mapped-ram.rst | 4 ++--
docs/devel/testing/acpi-bits.rst | 26 +++++++++++++-------------
docs/specs/fw_cfg.rst | 4 ++--
docs/specs/rapl-msr.rst | 25 ++++++++++++-------------
8 files changed, 38 insertions(+), 39 deletions(-)
--
2.46.2
next reply other threads:[~2024-10-11 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 11:12 Paolo Bonzini [this message]
2024-10-11 11:12 ` [PATCH v2 1/3] docs: fix invalid footnote syntax Paolo Bonzini
2024-10-11 11:12 ` [PATCH v2 2/3] docs: avoid footnotes consisting of just URLs Paolo Bonzini
2024-10-11 11:44 ` Peter Maydell
2024-10-11 11:12 ` [PATCH v2 3/3] docs: use consistent markup for footnotes Paolo Bonzini
2024-10-11 12:27 ` [PATCH v2 0/3] docs: fix and cleanup footnotes Peter Maydell
2024-10-11 15:32 ` Paolo Bonzini
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=20241011111249.47530-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).