On 19/1/26 09:19, Thomas Huth wrote:
On 16/01/2026 19.31, Pierrick Bouvier wrote:
On 1/15/26 11:17 PM, Thomas Huth wrote:
On 15/01/2026 21.35, Pierrick Bouvier wrote:
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.
Signed-off-by: Pierrick Bouvier <[email protected]>
---
MAINTAINERS | 5 +++++
1 file changed, 5 insertions(+)
I don't think it is e.g. hard to filter for e-mails that have "docs/" in
the subject, so that's certainly not a problem. It's getting tricky for
huge series that e.g. have just one little change to the docs folder in
between. Some people will CC: the whole big series to you for that
little change in one of the patches - how do you filter for such series?
Having maintained a generic subsystem with a catch-all entry in the past
(I used to be the maintainer of the qtests, and we had a "F: tests/
qtest/" entry in MAINTAINERS for this), I often got CC:-ed on big patch
series that should rather go through the architecture maintainer's tree,
and since only single patches affected the qtest subsystem, this was
hard to filter, so I always got lots of unrelated patches in my Inbox in
which I was not really interested in.
You can use lorelei, i.e.:
https://lore.kernel.org/qemu-devel/?q=dfn:/docs/+AND+-s:PULL
See how to integrate with your client workflow:
https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started#maildir-or-imap
My mitigation was to add some "X:" lines to the qtest section in
MAINTAINERS ... but if someone has some better ideas how to deal with
such situations (e.g. if there are some clever ways to filter such
series out of your Inbox), I'd be grateful to hear about them!
Ditto i.e.:
https://lore.kernel.org/qemu-devel/?q=dfn:/docs/+AND+-s:PULL+AND+-dfn:/docs/devel
FWIW, for the functional testing framework, I organized the entry in
MAINTAINERS differently, there is no generic "F: tests/functional/" line
in the section, but rather only coverage for the shared files of the
framework ... the tests themselves should be covered by the individual
maintainers instead. This works much better for me there.
So I'm interested to know how the generic "F: docs/" entry will work out
for you once this patch got merged and some weeks have passed. Having a
BoF at the next KVM forum about this email workflow topic might be a
good idea, indeed.
Thomas
