From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Peter Krempa <pkrempa@redhat.com>,
Juan Quintela <quintela@redhat.com>, John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH for-5.2 v3 0/3] migration: Add block-bitmap-mapping parameter
Date: Thu, 13 Aug 2020 15:04:32 +0200 [thread overview]
Message-ID: <b9e83cd9-d998-dae0-ee72-72c4f8188dda@redhat.com> (raw)
In-Reply-To: <a0dd7ae5-1f8f-c07d-e6a1-508743885e55@virtuozzo.com>
[-- Attachment #1.1: Type: text/plain, Size: 484 bytes --]
On 12.08.20 16:38, Vladimir Sementsov-Ogievskiy wrote:
> Now this doesn't apply, as code changed a lot after my series
> "[PATCH v4 for-5.1 00/21] Fix error handling during bitmap postcopy"
> merged first.
Yeah, well. Yeah.
> I feel my responsibility for the mess with these series, so if you want
> I can try to rebase and post v4 of this one myself :)
I feel like rebasing is simpler than reviewing, so I’ll be egoistic and
choose the rebaser’s side.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-08-13 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 8:05 [PATCH for-5.2 v3 0/3] migration: Add block-bitmap-mapping parameter Max Reitz
2020-07-22 8:05 ` [PATCH for-5.2 v3 1/3] " Max Reitz
2020-08-12 14:32 ` Eric Blake
2020-08-13 13:03 ` Max Reitz
2020-07-22 8:05 ` [PATCH for-5.2 v3 2/3] iotests.py: Add wait_for_runstate() Max Reitz
2020-07-22 8:05 ` [PATCH for-5.2 v3 3/3] iotests: Test node/bitmap aliases during migration Max Reitz
2020-08-12 14:15 ` [PATCH for-5.2 v3 0/3] migration: Add block-bitmap-mapping parameter Max Reitz
2020-08-12 14:38 ` Vladimir Sementsov-Ogievskiy
2020-08-13 13:04 ` Max Reitz [this message]
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=b9e83cd9-d998-dae0-ee72-72c4f8188dda@redhat.com \
--to=mreitz@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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).