From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Promote NBD to supported, with new maintainer
Date: Mon, 10 Jul 2017 06:42:13 -0500 [thread overview]
Message-ID: <94f33acf-57b4-62b7-7121-4e1e27048224@redhat.com> (raw)
In-Reply-To: <20170710101604.GA19707@lemon.lan>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
On 07/10/2017 05:16 AM, Fam Zheng wrote:
> On Fri, 07/07 13:21, Eric Blake wrote:
>> We are promising more than just odd fixes, and Paolo is hoping
>> to offload the pull requests to me. Also, enough of NBD is related
>> to the block layer that it is worth including qemu-block on patches.
>
> Cool!
>
>> +Network Block Device (NBD)
>> +M: Eric Blake <eblake@redhat.com>
>> +M: Paolo Bonzini <pbonzini@redhat.com>
>> +L: qemu-block@nongnu.org
>> +S: Maintained
>> +F: block/nbd*
>> +F: nbd/
>> +F: include/block/nbd*
>> +F: qemu-nbd.c
>
> While we are at it, add qemu-nbd.texi when you send pull request, if you don't
> respin?
Will do.
>
>> +T: git git://repo.or.cz/qemu/ericb.git nbd
>
> Out of curiosity: Paolo is still in "M:", but his "T:" is gone. Intended?
Hmm, I didn't realize you could list two T: entries, but a quick check
shows that is the case for several co-maintained areas. Paolo, any
preference?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-07-10 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 18:21 [Qemu-devel] [PATCH] MAINTAINERS: Promote NBD to supported, with new maintainer Eric Blake
2017-07-10 10:01 ` Paolo Bonzini
2017-07-10 10:16 ` Fam Zheng
2017-07-10 11:42 ` Eric Blake [this message]
2017-07-10 11:42 ` Paolo Bonzini
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=94f33acf-57b4-62b7-7121-4e1e27048224@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).