All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Daniel Henrique Barboza" <danielhb413@gmail.com>
Cc: peter.maydell@linaro.org, groug@kaod.org, qemu-ppc@nongnu.org,
	qemu-devel@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] target/ppc, hw/ppc: Change maintainers
Date: Sat, 6 Nov 2021 00:00:29 +0100	[thread overview]
Message-ID: <d7c12a79-107d-dfe6-ad7b-fde51f64ddf1@kaod.org> (raw)
In-Reply-To: <880124b9-5cd1-7fcb-fdc6-3d3f8a1da2b6@amsat.org>

> 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"?
> 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. 

Lotus Notes was not designed for patch communication. You don't want
me to send patches with it I assure you :)

> I don't
> mind the email technical detail, but I am curious about the status
> and expectations.

We have other IBM commitments. IBM is willing to share some/most of
our time for QEMU-PPC maintenance.

What we are going do will depend on inputs really. We have pseries
and KVM in focus because there is still business using the software
stack. TCG is extremely useful for pseries and powernv. We clearly
want to keep that running and improve it. Some parts have been barely
touched (and probably used) in the last 15 years. I think we should
drop some support to modernize the useful parts and ease maintenance.

Thanks,

C.



  parent reply	other threads:[~2021-11-05 23:02 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é
2021-11-05 23:00     ` Cédric Le Goater [this message]
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=d7c12a79-107d-dfe6-ad7b-fde51f64ddf1@kaod.org \
    --to=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=f4bug@amsat.org \
    --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 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.