From: Glauber Costa <glommer@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kwolf@redhat.com, aliguori@us.ibm.com, kvm@vger.kernel.org,
qemu-devel@nongnu.org, blauwirbel@gmail.com, avi@redhat.com
Subject: [Qemu-devel] Re: [PATCHv5 0/5] qemu misc save/load fixes
Date: Mon, 6 Jul 2009 15:34:56 -0300 [thread overview]
Message-ID: <20090706183456.GJ3528@poweredge.glommer> (raw)
In-Reply-To: <20090705125809.GA5417@redhat.com>
On Sun, Jul 05, 2009 at 03:58:09PM +0300, Michael S. Tsirkin wrote:
> Anthony, please commit the following patches that fix save/load issues
> with qemu.git
They all seem fine to me.
prev parent reply other threads:[~2009-07-06 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 12:58 [Qemu-devel] [PATCHv5 0/5] qemu misc save/load fixes Michael S. Tsirkin
2009-07-05 18:11 ` Stuart Brady
2009-07-05 19:45 ` Michael S. Tsirkin
2009-07-06 18:34 ` Glauber Costa [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=20090706183456.GJ3528@poweredge.glommer \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).