From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Daniel Henrique Barboza <danielhb413@gmail.com>, clg@kaod.org
Cc: peter.maydell@linaro.org,
David Gibson <david@gibson.dropbear.id.au>,
qemu-ppc@nongnu.org, groug@kaod.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] target/ppc, hw/ppc: Change maintainers
Date: Sat, 6 Nov 2021 10:18:48 +0100 [thread overview]
Message-ID: <35a056f3-f074-a2a1-bf43-e24ba483d0d2@amsat.org> (raw)
In-Reply-To: <91972ce2-8d1f-f22e-c87f-45cb3c221b18@gmail.com>
On 11/5/21 21:05, Daniel Henrique Barboza wrote:
> On 11/5/21 16:16, Philippe Mathieu-Daudé wrote:
>> Hi Daniel,
>>
>> On 11/5/21 10:48, Daniel Henrique Barboza wrote:
>>> On 11/5/21 00:46, David Gibson wrote:
>>>> As our day jobs and interests have moved onto other things, Greg and I
>>>> have
>>>> been struggling to keep on top of maintainership of target/ppc and
>>>> associated pieces like the pseries and powernv machine types, with
>>>> their
>>>> platform specific devices.
>>>>
>>>> We've therefore discussed and plan to transfer maintainership to
>>>> Cédric Le
>>>> Goater (primary) and Daniel Henrique Barboza (backup). Cédric and
>>>> Daniel
>>>> have been actively contributing to the area for some time, and they're
>>>> supported in this by their current employer, IBM, who has an obvious
>>>> interest in the platform.
>>>
>>> Thank you and Greg and Red Hat for all the years of service supporting
>>> qemu-ppc in the community. IBM will shoulder this responsibility now.
>>
>> In term of the MAINTAINERS file:
>>
>> S: Status, one of the following:
>> Supported: Someone is actually paid to look after this.
>> Maintained: Someone actually looks after it.
>>
>> The PPC entries have a 'Maintained' status. You say "IBM will shoulder
>> this responsibility", does that mean the entries will be 'Supported'
>> as in "someone paid to look after them"?
>
> Yes. It's appropriate to change the PPC entries of this patch to
> "Supported"
> now.
This is a great news :)
>> I wonder because both Cédric and you have some commits with an IBM
>> email, but both are registering a non-IBM email as contact. I don't
>> mind the email technical detail, but I am curious about the status
>> and expectations.
>
> I had problems using IBM corporate email with mailing lists in the past,
> and started using this gmail account instead. I believe Cedric has a
> similar sob story.
>
> FWIW the contrib/gitdm/group-map-ibm file has both our emails there to
> indicate that we're IBM contributors.
OK this is how I understood it first then. Thanks for the clarification.
Regards,
Phil.
next prev parent reply other threads:[~2021-11-06 9:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 3:46 [PATCH] target/ppc, hw/ppc: Change maintainers David Gibson
2021-11-05 9:48 ` Daniel Henrique Barboza
2021-11-05 19:16 ` Philippe Mathieu-Daudé
2021-11-05 20:05 ` Daniel Henrique Barboza
2021-11-06 4:20 ` David Gibson
2021-11-06 8:28 ` Cédric Le Goater
2021-11-06 8:53 ` David Gibson
2021-11-07 20:15 ` Greg Kurz
2021-11-06 9:18 ` Philippe Mathieu-Daudé [this message]
2021-11-05 23:00 ` Cédric Le Goater
2021-11-06 9:22 ` Philippe Mathieu-Daudé
2021-11-06 16:55 ` Cédric Le Goater
2021-11-05 13:54 ` Cédric Le Goater
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=35a056f3-f074-a2a1-bf43-e24ba483d0d2@amsat.org \
--to=f4bug@amsat.org \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).