From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Report on MAINTAINERS coverage
Date: Thu, 18 Dec 2025 13:49:13 +0000 [thread overview]
Message-ID: <aUQGWes2pCSWTDfe@redhat.com> (raw)
In-Reply-To: <871pkrdi6w.fsf@pond.sub.org>
On Thu, Dec 18, 2025 at 02:37:43PM +0100, Markus Armbruster wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > On Thu, Dec 18, 2025 at 01:45:24PM +0100, Markus Armbruster wrote:
> >> Which unmaintained files are we still changing? Unmaintained files
> >> sorted by number of commits in the past year (since v9.2.0):
> >>
> >> $ for i in `cat unmaintained-files`; do echo -n "$i "; git-rev-list v9.2.0.. $i | wc -l; done | awk '{ printf "%7d %s\n", $2, $1 }' | sort -rn
> >>
> >> 107 tests/functional/meson.build
> >
> > Opps, that's a mistake. It should of course be under the
> > general maint heading "Functional testing framework"
>
> Thanks! I can patch that.
>
> What about the other uncovered files in tests/functional/?
> tests/functional/aarch64/meson.build
[snip many more]
I'd wildcard tests/functional/*/meson.build under the
general maint.
> tests/functional/acpi-bits/bits-config/bits-cfg.txt
> tests/functional/acpi-bits/bits-tests/smbios.py2
> tests/functional/acpi-bits/bits-tests/smilatency.py2
> tests/functional/acpi-bits/bits-tests/testacpi.py2
> tests/functional/acpi-bits/bits-tests/testcpuid.py2
I expected those to already be covered by:
ACPI/FUNCTIONAL/BIOSBITS
M: Ani Sinha <anisinha@redhat.com>
M: Michael S. Tsirkin <mst@redhat.com>
S: Supported
F: tests/functional/acpi-bits/*
F: tests/functional/x86_64/test_acpi_bits.py
F: docs/devel/testing/acpi-bits.rst
but I guess tests/functional/acpi-bits/* doesn't recurse
into subdirs ?
> tests/functional/arm/test_max78000fthr.py
Added by Thomas but not sure what maintainers category it should go
under.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-12-18 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 12:45 Report on MAINTAINERS coverage Markus Armbruster
2025-12-18 12:55 ` Daniel P. Berrangé
2025-12-18 13:37 ` Markus Armbruster
2025-12-18 13:49 ` Daniel P. Berrangé [this message]
2025-12-18 14:06 ` Thomas Huth
2025-12-18 14:12 ` Daniel P. Berrangé
2025-12-18 14:17 ` Thomas Huth
2025-12-18 15:25 ` Markus Armbruster
2025-12-18 16:08 ` Thomas Huth
2025-12-19 8:43 ` Markus Armbruster
2025-12-18 15:57 ` Stefan Weil via
2025-12-19 7:44 ` 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=aUQGWes2pCSWTDfe@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--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.