From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: MAINTAINERS still leaves more files uncovered than I'd like
Date: Mon, 2 Oct 2023 20:25:31 +0200 [thread overview]
Message-ID: <9312569b-75c8-e179-af95-42c4fae76807@redhat.com> (raw)
In-Reply-To: <89b74108-0379-97c8-455e-cb0c5058785c@linaro.org>
On 02/10/2023 08.18, Philippe Mathieu-Daudé wrote:
> Hi Markus,
>
> On 29/9/23 13:43, Markus Armbruster wrote:
>> Back in 2014 (time flies), I posted
>>
>> Subject: MAINTAINERS leaves too many files uncovered
>> Message-ID: <87mw8rumhb.fsf@blackfin.pond.sub.org>
>> https://lore.kernel.org/qemu-devel/87mw8rumhb.fsf@blackfin.pond.sub.org/
>>
>> I updated my findings in 2015, 2016 (at commit e00da552a0d), and 2018
>> (at v3.1.0-rc2). This is another update, at commit 36e9aab3c56.
>>
>> Unsurprisingly, the number of files in the tree
>>
>> $ git-ls-files | wc -l
>>
>> grows over time:
>>
>> year 2014 2015 2016 2018 2023
>> # 3746 4387 4921 6461 9788
>>
>> Looks exponential to me, doubling every seven years or so.
>>
>> The number of .c files has grown more slowly:
>>
>> year 2014 2015 2016 2018 2023
>> # 1836 1945 2132 2633 3588
>>
>> The number of .c files not covered by MAINTAINERS
>
> [...]
>
>> hw/sensor/dps310.c
>> hw/sensor/emc141x.c
>> hw/sensor/lsm303dlhc_mag.c
>> hw/sensor/max31785.c
>> hw/sensor/meson.build
>> hw/sensor/tmp105.c
>> hw/sensor/tmp421.c
>
> I sent a patch for these but the community didn't
> seem very interested back then:
> https://lore.kernel.org/qemu-devel/20230220110235.24472-1-philmd@linaro.org/
As long as nobody complains, I'd say just go for it and put it in your next
pull request :-)
Thomas
next prev parent reply other threads:[~2023-10-02 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 11:43 MAINTAINERS still leaves more files uncovered than I'd like Markus Armbruster
2023-09-29 12:05 ` Cornelia Huck
2023-09-29 12:29 ` Thomas Huth
2023-09-29 14:35 ` Cornelia Huck
2023-10-02 6:18 ` Philippe Mathieu-Daudé
2023-10-02 18:25 ` Thomas Huth [this message]
2023-10-02 6:20 ` Philippe Mathieu-Daudé
2023-10-05 13:46 ` Markus Armbruster
2023-10-02 11:35 ` Cédric Le Goater
2023-10-05 13:50 ` 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=9312569b-75c8-e179-af95-42c4fae76807@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=philmd@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).