From: Richard Henderson <richard.henderson@linaro.org>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PULL 0/1] QAPI patches patches for 2024-08-27
Date: Thu, 29 Aug 2024 08:30:47 +1000 [thread overview]
Message-ID: <02ff2d1e-d5f7-4e98-9758-aa39f58bae6b@linaro.org> (raw)
In-Reply-To: <20240827103532.799039-1-armbru@redhat.com>
On 8/27/24 20:35, Markus Armbruster wrote:
> I'm nominating this fix for v9.1 because it can only affect generated
> documentation, and CI should protect us from surprise build breaks.
> Feel free to delay it to v9.2 if you think even that is too much risk
> or simply too much trouble to be worthwhile.
>
> The following changes since commit afaee42f777bc359db95f692804f7fc7e12c0c02:
>
> Merge tag 'pull-nbd-2024-08-26' of https://repo.or.cz/qemu/ericb into staging (2024-08-27 07:06:42 +1000)
>
> are available in the Git repository at:
>
> https://repo.or.cz/qemu/armbru.git tags/pull-qapi-2024-08-27
>
> for you to fetch changes up to 43e0d14ee09a0565adcf4ce5f35be79695958fb0:
>
> docs/sphinx: fix extra stuff in TOC after freeform QMP sections (2024-08-27 11:10:58 +0200)
>
> ----------------------------------------------------------------
> QAPI patches patches for 2024-08-27
>
> ----------------------------------------------------------------
> John Snow (1):
> docs/sphinx: fix extra stuff in TOC after freeform QMP sections
>
> docs/sphinx/qapidoc.py | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
Applied, thanks. Please update https://wiki.qemu.org/ChangeLog/9.1 as appropriate.
r~
prev parent reply other threads:[~2024-08-28 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 10:35 [PULL 0/1] QAPI patches patches for 2024-08-27 Markus Armbruster
2024-08-27 10:35 ` [PULL 1/1] docs/sphinx: fix extra stuff in TOC after freeform QMP sections Markus Armbruster
2024-08-28 22:30 ` Richard Henderson [this message]
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=02ff2d1e-d5f7-4e98-9758-aa39f58bae6b@linaro.org \
--to=richard.henderson@linaro.org \
--cc=armbru@redhat.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 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).