From: Richard Henderson <richard.henderson@linaro.org>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PULL v2 00/17] QAPI patches patches for 2023-05-09
Date: Wed, 10 May 2023 15:59:45 +0100 [thread overview]
Message-ID: <e94e5411-66de-3aa6-3ed2-f16154ec5294@linaro.org> (raw)
In-Reply-To: <20230510081224.3588673-1-armbru@redhat.com>
On 5/10/23 09:12, Markus Armbruster wrote:
> The following changes since commit 792f77f376adef944f9a03e601f6ad90c2f891b2:
>
> Merge tag 'pull-loongarch-20230506' of https://gitlab.com/gaosong/qemu into staging (2023-05-06 08:11:52 +0100)
>
> are available in the Git repository at:
>
> https://repo.or.cz/qemu/armbru.git tags/pull-qapi-2023-05-09-v2
>
> for you to fetch changes up to a937b6aa739f65f2cae2ad9a7eb65a309ad2a359:
>
> qapi: Reformat doc comments to conform to current conventions (2023-05-10 10:01:01 +0200)
>
> ----------------------------------------------------------------
> QAPI patches patches for 2023-05-09
>
> ----------------------------------------------------------------
> Markus Armbruster (17):
> docs/devel/qapi-code-gen: Clean up use of quotes a bit
> docs/devel/qapi-code-gen: Turn FIXME admonitions into comments
> qapi: Fix crash on stray double quote character
> meson: Fix to make QAPI generator output depend on main.py
> Revert "qapi: BlockExportRemoveMode: move comments to TODO"
> sphinx/qapidoc: Do not emit TODO sections into user manuals
> qapi: Tidy up a slightly awkward TODO comment
> qapi/dump: Indent bulleted lists consistently
> tests/qapi-schema/doc-good: Improve a comment
> tests/qapi-schema/doc-good: Improve argument description tests
> qapi: Fix argument description indentation stripping
> qapi: Rewrite parsing of doc comment section symbols and tags
> qapi: Relax doc string @name: description indentation rules
> qapi: Section parameter @indent is no longer used, drop
> docs/devel/qapi-code-gen: Update doc comment conventions
> qga/qapi-schema: Reformat doc comments to conform to current conventions
> qapi: Reformat doc comments to conform to current conventions
I didn't notice earlier, because centos-stream-8-x86_64 failure is optional,
but this has another error:
https://gitlab.com/qemu-project/qemu/-/jobs/4258751398#L4649
Exception occurred:
File
"/home/gitlab-runner/builds/Jpwtyaz7/0/qemu-project/qemu/docs/../scripts/qapi/parser.py",
line 566, in QAPIDoc
def _match_at_name_colon(string: str) -> re.Match:
AttributeError: module 're' has no attribute 'Match'
r~
next prev parent reply other threads:[~2023-05-10 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 8:12 [PULL v2 00/17] QAPI patches patches for 2023-05-09 Markus Armbruster
2023-05-10 8:12 ` [PULL v2 12/17] qapi: Rewrite parsing of doc comment section symbols and tags Markus Armbruster
2023-05-16 12:07 ` Igor Mammedov
2023-05-16 13:59 ` Markus Armbruster
2023-05-10 8:12 ` [PULL v2 13/17] qapi: Relax doc string @name: description indentation rules Markus Armbruster
2023-05-10 8:12 ` [PULL v2 14/17] qapi: Section parameter @indent is no longer used, drop Markus Armbruster
2023-05-10 13:51 ` [PULL v2 00/17] QAPI patches patches for 2023-05-09 Richard Henderson
2023-05-10 14:59 ` Richard Henderson [this message]
2023-05-10 15:22 ` Markus Armbruster
2023-05-11 11:11 ` Markus Armbruster
2023-05-11 11:17 ` Richard Henderson
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=e94e5411-66de-3aa6-3ed2-f16154ec5294@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).