From: Markus Armbruster <armbru@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org, "Phil Mathieu-Daudé" <philmd@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Fabiano Rosas" <farosas@suse.de>
Subject: Re: [PATCH] MAINTAINERS: add maintainer for docs/
Date: Tue, 20 Jan 2026 11:49:30 +0100 [thread overview]
Message-ID: <87o6moh83p.fsf@pond.sub.org> (raw)
In-Reply-To: <b33bfa26-5f41-4bad-9911-37d0b58618dd@linaro.org> (Pierrick Bouvier's message of "Mon, 19 Jan 2026 10:47:49 -0800")
Pierrick Bouvier <pierrick.bouvier@linaro.org> writes:
[...]
> I tend to see series as an atomic change, expecting them to be pulled as a whole. Thus, I expect, maybe wrongly, that isolated doc patches will be pulled with the concerned series.
Your expectation matches how I work as overall QAPI schema maintainer.
Most patch series modifying qapi/ aren't about the QAPI schema. I
routinely review just the QAPI part, and leave the remainder and the
merging to the actual subject matter maintainers.
[...]
next prev parent reply other threads:[~2026-01-20 10:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 20:35 [PATCH] MAINTAINERS: add maintainer for docs/ Pierrick Bouvier
2026-01-16 6:29 ` Markus Armbruster
2026-01-16 7:17 ` Thomas Huth
2026-01-16 18:31 ` Pierrick Bouvier
2026-01-19 8:19 ` Thomas Huth
2026-01-19 18:47 ` Pierrick Bouvier
2026-01-20 10:49 ` Markus Armbruster [this message]
2026-01-20 6:21 ` Philippe Mathieu-Daudé
2026-01-16 9:52 ` Daniel P. Berrangé
2026-01-16 18:28 ` Pierrick Bouvier
2026-01-16 11:37 ` Alex Bennée
2026-01-16 18:33 ` Pierrick Bouvier
2026-01-21 17:12 ` Alex Bennée
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=87o6moh83p.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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.