qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Josh Durgin <josh.durgin@dreamhost.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Stefan Weil <sw@weilnetz.de>, Jeff Cody <jcody@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Ronnie Sahlberg <ronniesahlberg@gmail.com>,
	Fam Zheng <famz@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>,
	MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>,
	Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: add block driver sub-maintainers
Date: Mon, 21 Oct 2013 22:15:24 +0100	[thread overview]
Message-ID: <20131021211524.GR1887@redhat.com> (raw)
In-Reply-To: <CA+aC4kt1rScUvggubQrrYXJcND3v7z6G+tpBYW37O5VSW2BAxQ@mail.gmail.com>

On Mon, Oct 21, 2013 at 09:19:42PM +0100, Anthony Liguori wrote:
> On Mon, Oct 21, 2013 at 2:26 PM, Stefan Hajnoczi <stefanha@redhat.com> 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>
> 
> Acked-by: Anthony Liguori <aliguori@amazon.com>
> 
> Although you certainly don't need it.  I assume everything is still
> going to flow through the block tree or are you guys looking for these
> folks to submit their own pull requests to me?

Speaking for myself, I would prefer that changes to block/ssh.c go
through the ordinary qemu-devel mailing list or Stefan's tree, and NOT
depend on me.  However devs can CC me on patches to see if I can help
to ACK them.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org

  reply	other threads:[~2013-10-21 21:15 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 [this message]
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

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=20131021211524.GR1887@redhat.com \
    --to=rjones@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=anthony@codemonkey.ws \
    --cc=famz@redhat.com \
    --cc=jcody@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=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).