From: Juan Quintela <quintela@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, lvivier@redhat.com, dgilbert@redhat.com,
peterx@redhat.com
Subject: Re: [Qemu-devel] [PULL 0/5] Migration pull request
Date: Mon, 15 May 2017 19:17:35 +0200 [thread overview]
Message-ID: <8760h2dopc.fsf@secure.mitica> (raw)
In-Reply-To: <20170515135848.GL1201@stefanha-x1.localdomain> (Stefan Hajnoczi's message of "Mon, 15 May 2017 14:58:48 +0100")
Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Fri, May 12, 2017 at 05:52:44PM +0200, Juan Quintela wrote:
>> Hi
>>
>>
>
> Thanks, applied to my staging tree:
> https://github.com/stefanha/qemu/commits/staging
Hi
As fast as I sent the PULL request, more comments appeared.
What do you preffer?
- drop the whole PULL request?
- drop the patch: migration: Create block capabilities for shared and enable
it has zero conflicts with the other patches
- let the PULL alone and I will sent fixes on top of that?
I would preffer option two, but that is up to you.
Sorry for the inconvenience.
Later, Juan.
next prev parent reply other threads:[~2017-05-15 17:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 15:52 [Qemu-devel] [PULL 0/5] Migration pull request Juan Quintela
2017-05-12 15:52 ` [Qemu-devel] [PULL 1/5] migration: Fix regression with compression threads Juan Quintela
2017-05-12 15:52 ` [Qemu-devel] [PULL 2/5] migration: Pass Error ** argument to {save, load}_vmstate Juan Quintela
2017-05-12 15:52 ` [Qemu-devel] [PULL 3/5] ram: Rename RAM_SAVE_FLAG_COMPRESS to RAM_SAVE_FLAG_ZERO Juan Quintela
2017-05-12 15:52 ` [Qemu-devel] [PULL 4/5] migration: Create block capabilities for shared and enable Juan Quintela
2017-05-12 15:52 ` [Qemu-devel] [PULL 5/5] migration: Create migration/blocker.h Juan Quintela
2017-05-15 13:58 ` [Qemu-devel] [PULL 0/5] Migration pull request Stefan Hajnoczi
2017-05-15 14:52 ` Eric Blake
2017-05-15 17:17 ` Juan Quintela [this message]
2017-05-16 14:35 ` Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2018-06-04 4:21 Juan Quintela
2018-06-04 4:29 ` no-reply
2018-06-04 7:30 ` Juan Quintela
2018-06-04 13:24 ` Peter Maydell
2017-06-14 11:51 [Qemu-devel] [PULL 0/5] Migration PULL request Juan Quintela
2017-06-15 11:56 ` Peter Maydell
2017-05-31 9:15 [Qemu-devel] [PULL 0/5] Migration pull request Juan Quintela
2017-06-01 14:50 ` Peter Maydell
2015-11-04 12:48 Juan Quintela
2015-11-05 10:48 ` 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=8760h2dopc.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).