From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Dmitry Eremin-Solenikov" <dbaryshkov@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Add an entry for the 'collie' machine
Date: Wed, 7 Nov 2018 19:42:11 +0000 [thread overview]
Message-ID: <CAFEAcA_N7zeuMGGvUBC6xu-AK2gH0n+aNwJOkhs7yWFx_3DbsQ@mail.gmail.com> (raw)
In-Reply-To: <4b0e9b3f-5d88-9ef2-d0c5-f241067001d0@redhat.com>
On 7 November 2018 at 19:39, Thomas Huth <thuth@redhat.com> wrote:
> On 2018-11-07 17:08, Markus Armbruster wrote:
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>
>>> On 6 November 2018 at 18:52, Thomas Huth <thuth@redhat.com> wrote:
>>>> On 2018-11-06 19:49, Philippe Mathieu-Daudé wrote:
>>>>> On 6/11/18 19:17, Thomas Huth wrote:
>>>>>> There is no active maintainer, but since Peter is picking up
>>>>>> patches via qemu-arm@nongnu.org, I think we could at least use
>>>>>> "Odd Fixes" as status here.
>>>>>
>>>>> This looks more as "Orphan" to me...
>>>>
>>>> I'll leave it up to Peter for the final decision...
>>>
>>> I think we're not very consistent[*] in our usage of the various
>>> statuses in the MAINTAINERS file. I guess "Odd Fixes" makes
>>> sense in that, well, if you send a patch to this
>>> code and cc me I'll review it and put it in the tree. (This
>>> is true of any of the arm boards we have.)
>>>
>>> [*] We have one thing tagged Orphan, which is bsd-user/,
>>> and some things tagged Odd Fixes with no listed maintainer,
>>> and some things tagged Odd Fixes which are in practice more
>>> like Orphan (for instance sh4), and we list "fpu/" as
>>> Odd Fixes despite having given it a pretty thorough
>>> overhaul very recently, and so on...
>>>
>>> If you wanted a mechanizable rule, you could try something
>>> like "every file which is in status Odd Fixes or better
>>> must list with M: at least one named individual who has
>>> submitted a pull request in the last nine months" :-)
>>
>> Sounds like an excellent idea to me!
>
> Well, for me "odd fixes" means that there is someone around who might
> pick up the patch and throw it into a PULL request. "Orphan" means it's
> mostly in vain to send patches for this subsystem, since there is nobody
> going to pick up your patch. So for the ARM boards, I'd say that "odd
> fixes" is a better choice, since Peter still picks up most of the
> patches via the "L: qemu-arm@nongnu.org" (big thanks for this, by the way!).
I think there should be a named person, though. A list
isn't a maintainer (at least not for the big whole
subsystem lists we have).
thanks
-- PMM
next prev parent reply other threads:[~2018-11-07 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 18:17 [Qemu-devel] [PATCH] MAINTAINERS: Add an entry for the 'collie' machine Thomas Huth
2018-11-06 18:49 ` Philippe Mathieu-Daudé
2018-11-06 18:52 ` Thomas Huth
2018-11-06 18:58 ` Peter Maydell
2018-11-07 16:08 ` Markus Armbruster
2018-11-07 19:39 ` Thomas Huth
2018-11-07 19:42 ` Peter Maydell [this message]
2018-11-08 7:04 ` Markus Armbruster
2018-11-08 13:44 ` Peter Maydell
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=CAFEAcA_N7zeuMGGvUBC6xu-AK2gH0n+aNwJOkhs7yWFx_3DbsQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--cc=dbaryshkov@gmail.com \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--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 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).