From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stuart Brady <sdbrady@ntlworld.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv5 0/5] qemu misc save/load fixes
Date: Sun, 5 Jul 2009 22:45:58 +0300 [thread overview]
Message-ID: <20090705194558.GA4043@redhat.com> (raw)
In-Reply-To: <20090705181100.GA1638@miranda.arrow>
On Sun, Jul 05, 2009 at 07:11:00PM +0100, Stuart Brady wrote:
> On Sun, Jul 05, 2009 at 03:58:09PM +0300, Michael S. Tsirkin wrote:
> > Changes since v3:
> > Missing braces reported by Blue Swirl
>
> *ahem* -- I reported it too, y'know. ;-))
Sorry, missed that. But it's fixed now :)
Pls Cc me when you want my attention - this makes
the message highlighted so it's harder for me to miss.
> BTW, s/braces/brackets/ (or parenthesis, if you prefer)...
>
> Cheers,
> --
> Stuart Brady
>
next prev parent reply other threads:[~2009-07-05 19:46 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 [this message]
2009-07-06 18:34 ` [Qemu-devel] " Glauber Costa
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=20090705194558.GA4043@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sdbrady@ntlworld.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).