From: Jeff Cody <jcody@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Josh Durgin <josh.durgin@dreamhost.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Stefan Weil <sw@weilnetz.de>,
qemu-devel@nongnu.org, "Richard W.M. Jones" <rjones@redhat.com>,
Anthony Liguori <aliguori@amazon.com>,
Paolo Bonzini <pbonzini@redhat.com>, Fam Zheng <famz@redhat.com>,
MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: add block driver sub-maintainers
Date: Wed, 23 Oct 2013 08:33:39 -0400 [thread overview]
Message-ID: <20131023123339.GA16816@localhost.localdomain> (raw)
In-Reply-To: <1382361975-27624-1-git-send-email-stefanha@redhat.com>
On Mon, Oct 21, 2013 at 02:26:15PM +0100, Stefan Hajnoczi wrote:
> There are a number of contributors who maintain block drivers (image
> formats and protocols). They should be listed in the MAINTAINERS file
> so that get_maintainer.pl lists them.
>
> Note that commits are still merged through Kevin or Stefan's block tree
> but the block driver sub-maintainers are usually the ones to review
> patches.
>
> Acked-by: Kevin Wolf <kwolf@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> MAINTAINERS | 38 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 77edacf..da18a23 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -857,3 +857,41 @@ Stable 0.10
> L: qemu-stable@nongnu.org
> T: git git://git.qemu-project.org/qemu-stable-0.10.git
> S: Orphan
> +
> +Block drivers
> +-------------
> +VMDK
> +M: Fam Zheng <famz@redhat.com>
> +S: Supported
> +F: block/vmdk.c
> +
> +RBD
> +M: Josh Durgin <josh.durgin@dreamhost.com>
> +S: Supported
> +F: block/rbd.c
> +
> +Sheepdog
> +M: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
> +S: Supported
> +F: block/sheepdog.c
> +
> +VHDX
> +M: Jeff Cody <jcody@redhat.com>
> +S: Supported
> +F: block/vhdx.c
This should probably be block/vhdx* instead
With that,
Acked-by: Jeff Cody <jcody@redhat.com>
> +
> +VDI
> +M: Stefan Weil <sw@weilnetz.de>
> +S: Maintained
> +F: block/vdi.c
> +
> +iSCSI
> +M: Ronnie Sahlberg <ronniesahlberg@gmail.com>
> +M: Paolo Bonzini <pbonzini@redhat.com>
> +S: Supported
> +F: block/iscsi.c
> +
> +SSH
> +M: Richard W.M. Jones <rjones@redhat.com>
> +S: Supported
> +F: block/ssh.c
> --
> 1.8.3.1
>
prev parent reply other threads:[~2013-10-23 12:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 13:26 [Qemu-devel] [PATCH] MAINTAINERS: add block driver sub-maintainers Stefan Hajnoczi
2013-10-21 14:02 ` Richard W.M. Jones
2013-10-21 18:06 ` Stefan Weil
2013-10-21 18:56 ` Josh Durgin
2013-10-21 20:19 ` Anthony Liguori
2013-10-21 21:15 ` Richard W.M. Jones
2013-10-22 8:17 ` Kevin Wolf
2013-10-23 6:19 ` MORITA Kazutaka
2013-10-23 6:51 ` MORITA Kazutaka
2013-10-23 6:59 ` Liu Yuan
2013-10-23 6:23 ` Paolo Bonzini
2013-10-24 10:11 ` Peter Lieven
2013-10-23 12:33 ` Jeff Cody [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=20131023123339.GA16816@localhost.localdomain \
--to=jcody@redhat.com \
--cc=aliguori@amazon.com \
--cc=famz@redhat.com \
--cc=josh.durgin@dreamhost.com \
--cc=kwolf@redhat.com \
--cc=morita.kazutaka@lab.ntt.co.jp \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).