From: Kevin Wolf <kwolf@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] MAINTAINERS: add block driver sub-maintainers
Date: Wed, 13 Nov 2013 17:26:47 +0100 [thread overview]
Message-ID: <20131113162647.GH2633@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <20131113161712.GC22807@localhost.localdomain>
Am 13.11.2013 um 17:17 hat Jeff Cody geschrieben:
> On Wed, Nov 13, 2013 at 10:33:10AM +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>
> > Acked-by: Richard W.M. Jones <rjones@redhat.com>
> > Acked-by: Stefan Weil <sw@weilnetz.de>
> > Acked-by: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
> > Acked-by: Paolo Bonzini <pbonzini@redhat.com>
> > Acked-by: Jeff Cody <jcody@redhat.com>
> > Acked-by: Anthony Liguori <aliguori@amazon.com>
> > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > +VHDX
> > +M: Jeff Cody <jcody@redhat.com>
> > +S: Supported
> > +F: block/vhdx.*
>
> This should be block/vhdx* instead, to pick up vhdx-endian.c and
> vhdx-log.c as well.
Thanks, fixed it locally.
Kevin
next prev parent reply other threads:[~2013-11-13 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 9:33 [Qemu-devel] [PATCH v2] MAINTAINERS: add block driver sub-maintainers Stefan Hajnoczi
2013-11-13 16:17 ` Jeff Cody
2013-11-13 16:26 ` Kevin Wolf [this message]
2013-11-14 9:19 ` Stefan Hajnoczi
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=20131113162647.GH2633@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=jcody@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).