From: Gerd Hoffmann <kraxel@redhat.com>
To: Yonit Halperin <yhalperi@redhat.com>
Cc: qemu-devel@nongnu.org, spice-devel@freedesktop.org
Subject: Re: [Qemu-devel] [PATCH v2 0/2] spice migration interface v2 (RHBZ 737921)
Date: Mon, 17 Oct 2011 12:00:30 +0200 [thread overview]
Message-ID: <4E9BFCBE.1030909@redhat.com> (raw)
In-Reply-To: <1318838599-15317-1-git-send-email-yhalperi@redhat.com>
On 10/17/11 10:03, Yonit Halperin wrote:
> Same as the previous series with a small fix to
> allow compliation without Spice disabled.
Replaced patches.
Thanks,
Gerd
prev parent reply other threads:[~2011-10-17 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 8:03 [Qemu-devel] [PATCH v2 0/2] spice migration interface v2 (RHBZ 737921) Yonit Halperin
2011-10-17 8:03 ` [Qemu-devel] [PATCH v2 1/2] spice: turn client_migrate_info to async Yonit Halperin
2011-10-17 8:03 ` [Qemu-devel] [PATCH v2 2/2] spice: support the new migration interface (spice 0.8.3) Yonit Halperin
2011-10-17 10:00 ` Gerd Hoffmann [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=4E9BFCBE.1030909@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@freedesktop.org \
--cc=yhalperi@redhat.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).