From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: qemu-devel@nongnu.org, "Phil Mathieu-Daudé" <philmd@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: [PATCH] MAINTAINERS: add maintainer for docs/
Date: Wed, 21 Jan 2026 17:12:39 +0000 [thread overview]
Message-ID: <87tsweopo8.fsf@draig.linaro.org> (raw)
In-Reply-To: <20260115203529.2713193-1-pierrick.bouvier@linaro.org> (Pierrick Bouvier's message of "Thu, 15 Jan 2026 12:35:29 -0800")
Pierrick Bouvier <pierrick.bouvier@linaro.org> writes:
> I would like to help maintaining qemu documentation and I've been
> invited by Alex to apply as maintainer.
>
> Files in docs/ that are already maintained will continue to be under
> their respective maintainer. The goal here is to have someone that can
> help on all other files that don't have an official maintainer.
Queued to for-11.0/maintainers-update, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2026-01-21 17:13 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
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 [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=87tsweopo8.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--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.