From: Peter Maydell <peter.maydell@linaro.org>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: Eric Blake <eblake@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
"open list:Block layer core" <qemu-block@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] STOP Re: [PULL 4/4] qmp: add nbd-server-remove
Date: Thu, 21 Dec 2017 13:13:21 +0000 [thread overview]
Message-ID: <CAFEAcA-Pd5wzSDttMumMizUTCh7oxzO-dodAMb1H9b5_x5R_7Q@mail.gmail.com> (raw)
In-Reply-To: <47a78a6e-cc5b-5ac5-1f80-222ecb4ee8c4@virtuozzo.com>
On 21 December 2017 at 09:07, Vladimir Sementsov-Ogievskiy
<vsementsov@virtuozzo.com> wrote:
> no, I've updated it, we discussed with Kevin that this approach is bad
To say that a pullreq is bad you need to reply to the cover letter,
there's no guarantee I'll notice a followup to one of the
individual patches in it. (As it happens I saw this email so
I'll take the pullreq out of the queue.)
thanks
-- PMM
next prev parent reply other threads:[~2017-12-21 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 1:35 [Qemu-devel] [PULL 0/4] NBD patches through 20 Dec Eric Blake
2017-12-21 1:35 ` [Qemu-devel] [PULL 1/4] nbd/server: Implement sparse reads atop structured reply Eric Blake
2017-12-21 1:35 ` [Qemu-devel] [PULL 2/4] nbd/server: Optimize final chunk of sparse read Eric Blake
2017-12-21 1:35 ` [Qemu-devel] [PULL 3/4] nbd/server: add additional assert to nbd_export_put Eric Blake
2017-12-21 1:36 ` [Qemu-devel] [PULL 4/4] qmp: add nbd-server-remove Eric Blake
2017-12-21 9:07 ` [Qemu-devel] STOP " Vladimir Sementsov-Ogievskiy
2017-12-21 9:10 ` Vladimir Sementsov-Ogievskiy
2017-12-21 14:01 ` Eric Blake
2017-12-21 13:13 ` Peter Maydell [this message]
2017-12-21 13:13 ` [Qemu-devel] [PULL 0/4] NBD patches through 20 Dec Peter Maydell
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=CAFEAcA-Pd5wzSDttMumMizUTCh7oxzO-dodAMb1H9b5_x5R_7Q@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@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).