From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: michael.roth@amd.com, jsnow@redhat.com, peter.maydell@linaro.org
Subject: [PATCH 0/2] qapi-domain: Typos and MAINTAINERS
Date: Tue, 29 Jul 2025 11:16:40 +0200 [thread overview]
Message-ID: <20250729091642.3513895-1-armbru@redhat.com> (raw)
Markus Armbruster (2):
docs/qapi-domain: Fix typos
MAINTAINERS: Cover docs/devel/qapi-domain.rst properly
MAINTAINERS | 1 +
docs/devel/qapi-domain.rst | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.49.0
next reply other threads:[~2025-07-29 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 9:16 Markus Armbruster [this message]
2025-07-29 9:16 ` [PATCH 1/2] docs/qapi-domain: Fix typos Markus Armbruster
2025-07-29 12:05 ` Manos Pitsidianakis
2025-07-29 9:16 ` [PATCH 2/2] MAINTAINERS: Cover docs/devel/qapi-domain.rst properly Markus Armbruster
2025-07-29 12:09 ` Manos Pitsidianakis
2025-07-29 12:32 ` Markus Armbruster
2025-07-29 12:59 ` Markus Armbruster
2025-07-29 13:00 ` Philippe Mathieu-Daudé
2025-07-29 13:14 ` [PATCH 0/2] qapi-domain: Typos and MAINTAINERS Markus Armbruster
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=20250729091642.3513895-1-armbru@redhat.com \
--to=armbru@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 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).