From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eric Farman <farman@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH RFC] MAINTAINERS: split out s390x sections
Date: Mon, 20 Dec 2021 18:31:34 +0100 [thread overview]
Message-ID: <0a830f15-bdca-02b2-d36d-2063e31c5e75@redhat.com> (raw)
In-Reply-To: <20211220115419.308463-1-cohuck@redhat.com>
On 12/20/21 12:54, Cornelia Huck wrote:
> Split out some more specialized devices etc., so that we can build
> smarter lists of people to be put on cc: in the future.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
>
> As discussed offlist. Some notes:
> - The new sections have inherited the maintainers of the sections
> they have been split out of (except where people had already
> volunteered). That's easy to change, obviously, and I hope that
> the cc: list already contains people who might have interest in
> volunteering for some sections.
> - I may not have gotten the F: patterns correct, please double check.
> - I'm also not sure about where in the MAINTAINERS file the new
> sections should go; if you have a better idea, please speak up.
> - Also, if you have better ideas regarding the sections, please
> speak up as well :)
> - Pull requests will probably continue the same way as now (i.e.
> patches picked up at the top level and then sent, except for some
> things like tcg which may go separately.) Not sure if it would
> make sense to try out the submaintainer pull request model again,
> I don't think it made life easier in the past, and now we have
> the b4 tool to pick patches easily anyway. It might be a good
> idea to check which of the tree locations should stay, or if we
> want to have new ones.
>
> ---
> MAINTAINERS | 86 ++++++++++++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 75 insertions(+), 11 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2021-12-20 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 11:54 [PATCH RFC] MAINTAINERS: split out s390x sections Cornelia Huck
2021-12-20 17:31 ` Philippe Mathieu-Daudé [this message]
2021-12-20 19:27 ` David Hildenbrand
2021-12-21 9:44 ` Christian Borntraeger
2021-12-21 10:09 ` Thomas Huth
2021-12-21 16:11 ` Cornelia Huck
2021-12-22 9:33 ` Halil Pasic
2021-12-21 14:14 ` Halil Pasic
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=0a830f15-bdca-02b2-d36d-2063e31c5e75@redhat.com \
--to=philmd@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.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).