From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, Cleber Rosa <crosa@redhat.com>,
Michael Roth <michael.roth@amd.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH 2/5] docs/qapidoc: linting fixes
Date: Tue, 25 Mar 2025 08:36:02 +0100 [thread overview]
Message-ID: <87y0wtpnod.fsf@pond.sub.org> (raw)
In-Reply-To: <20250321222347.299121-3-jsnow@redhat.com> (John Snow's message of "Fri, 21 Mar 2025 18:23:44 -0400")
John Snow <jsnow@redhat.com> writes:
> This restores the linting baseline in qapidoc. The order of some imports
> have changed slightly due to configuring isort a little better: isort
Changed since when / what?
> was having difficulty understanding that "compat" and "qapidoc_legacy"
> were local modules because docs/sphinx "isn't a python package".
>
> Signed-off-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2025-03-25 7:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 22:23 [PATCH 0/5] python: add QAPI and qapidoc et al to python linter tests John Snow
2025-03-21 22:23 ` [PATCH 1/5] qapi: Add some pylint ignores John Snow
2025-03-21 22:23 ` [PATCH 2/5] docs/qapidoc: linting fixes John Snow
2025-03-25 7:36 ` Markus Armbruster [this message]
2025-03-25 16:49 ` John Snow
2025-03-26 6:04 ` Markus Armbruster
2025-03-21 22:23 ` [PATCH 3/5] python: update missing dependencies from minreqs John Snow
2025-03-26 6:08 ` Markus Armbruster
2025-03-26 20:12 ` John Snow
2025-03-27 5:36 ` Markus Armbruster
2025-03-31 18:39 ` John Snow
2025-03-21 22:23 ` [PATCH 4/5] python: add qapi static analysis tests John Snow
2025-03-25 7:52 ` Markus Armbruster
2025-03-25 16:56 ` John Snow
2025-03-26 6:12 ` Markus Armbruster
2025-03-26 20:16 ` John Snow
2025-03-21 22:23 ` [PATCH 5/5] qapi: delete un-needed python static analysis configs John Snow
2025-03-25 8:05 ` Markus Armbruster
2025-03-25 17:36 ` John Snow
2025-03-26 7:18 ` Markus Armbruster
2025-03-26 20:24 ` John Snow
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=87y0wtpnod.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=michael.roth@amd.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 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.