qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: borntraeger@de.ibm.com, agraf@suse.de, rth@twiddle.net,
	david@redhat.com, thuth@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] s390x: maintainership reorg
Date: Thu, 8 Feb 2018 16:14:14 +0100	[thread overview]
Message-ID: <20180208161414.073ac2c2.cohuck@redhat.com> (raw)
In-Reply-To: <20180207155531.28446-1-cohuck@redhat.com>

On Wed,  7 Feb 2018 16:55:28 +0100
Cornelia Huck <cohuck@redhat.com> wrote:

> Hi,
> 
> s390x maintainership is currently a bit like a huge pile of stuff routed
> through one person who is not even listed as the maintainer for some
> of the areas. Let's try to clean this up a bit.
> 
> Patch 1 is basically making official what I actually have been doing in
> the last months; that is, acting as the overall s390x maintainer. There
> does not seem to be the concept of "overall arch maintainer" in MAINTAINERS
> so far, so I added it.
> 
> Where I want to go is basically a submaintainership model for s390x,
> i.e. that I integrate the work in various areas and send it on. Patch 2
> serves as a step in that direction, as Thomas has volunteered to look
> after the s390-ccw bios (thanks!)
> 
> If that works out well, I plan to split out other parts as well. That
> would make a lot of sense for those parts which I lack documentation
> for, and also for parts where other folks could do a good job as well.
> 
> Speaking of other people: Patch 3 adds David as an additional maintainer
> for tcg (thanks!).
> 
> Cornelia Huck (3):
>   MAINTAINERS: add myself as overall s390x maintainer
>   MAINTAINERS: reorganize s390-ccw bios maintainership
>   MAINTAINERS: add David as additional tcg/s390 maintainer
> 
>  MAINTAINERS | 35 +++++++++++++++++++++++++++++++++--
>  1 file changed, 33 insertions(+), 2 deletions(-)
> 

Queued to s390-next.

      parent reply	other threads:[~2018-02-08 15:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 15:55 [Qemu-devel] [PATCH 0/3] s390x: maintainership reorg Cornelia Huck
2018-02-07 15:55 ` [Qemu-devel] [PATCH 1/3] MAINTAINERS: add myself as overall s390x maintainer Cornelia Huck
2018-02-07 16:24   ` Philippe Mathieu-Daudé
2018-02-07 16:28     ` Cornelia Huck
2018-02-07 18:19   ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-02-08 12:17   ` [Qemu-devel] " David Hildenbrand
2018-02-08 15:25   ` Daniel Henrique Barboza
2018-02-07 15:55 ` [Qemu-devel] [PATCH 2/3] MAINTAINERS: reorganize s390-ccw bios maintainership Cornelia Huck
2018-02-07 18:21   ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-02-07 18:47   ` [Qemu-devel] " Thomas Huth
2018-02-07 15:55 ` [Qemu-devel] [PATCH 3/3] MAINTAINERS: add David as additional tcg/s390 maintainer Cornelia Huck
2018-02-08 12:09   ` David Hildenbrand
2018-02-08 15:14 ` Cornelia Huck [this message]

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=20180208161414.073ac2c2.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --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).