From: Eric Blake <eblake@redhat.com>
To: Nir Soffer <nsoffer@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-block <qemu-block@nongnu.org>
Subject: Re: [PATCH] nbd: server: Report holes for raw images
Date: Wed, 3 Mar 2021 15:51:14 -0600 [thread overview]
Message-ID: <7e9dc71e-d412-bf57-c708-b470893aac9d@redhat.com> (raw)
In-Reply-To: <CAMRbyysiNe1J54a1nQ0UOJGU26nTZQ6yqVGLVeUd4LV-n-LJ_Q@mail.gmail.com>
On 3/3/21 3:45 PM, Nir Soffer wrote:
>>>>
>>>> I'll wait a few days for any other reviewer commentary before taking
>>>> this through my NBD tree.
>>>>
>>
>> And thanks for CCing me. Hmm, maybe, I'll suggest myself as co-maintainer
>> for NBD?
Vladimir, I'd be happy if you want to do that in a separate patch
(you're already a co-maintainer on block bitmaps, which are somewhat
related).
>
>
> Kevin, Max, are you ok with this change?
I guess that means I should send my NBD pull request sooner rather than
later, since it's been a few days with no other comments?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-03-03 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 16:07 [PATCH] nbd: server: Report holes for raw images Nir Soffer
2021-02-19 16:42 ` Eric Blake
2021-02-19 16:58 ` Eric Blake
2021-02-25 18:50 ` Vladimir Sementsov-Ogievskiy
2021-03-03 21:45 ` Nir Soffer
2021-03-03 21:51 ` Eric Blake [this message]
2021-03-04 12:22 ` Kevin Wolf
2021-02-25 18:15 ` Vladimir Sementsov-Ogievskiy
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=7e9dc71e-d412-bf57-c708-b470893aac9d@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=nsoffer@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).