From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 1.1-rc3 release
Date: Tue, 22 May 2012 18:13:11 +0300 [thread overview]
Message-ID: <4FBBAD07.9030106@redhat.com> (raw)
In-Reply-To: <4FBBA384.4010803@us.ibm.com>
On 05/22/2012 05:32 PM, Anthony Liguori wrote:
> Known Issues:
>
> - There are no known release blockers in -rc3.
>
Please consider http://patchwork.ozlabs.org/patch/157995/ for merging
into 1.1.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-22 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 14:32 [Qemu-devel] [ANNOUNCE] QEMU 1.1-rc3 release Anthony Liguori
2012-05-22 15:09 ` Jan Kiszka
2012-05-22 15:33 ` Gerd Hoffmann
2012-05-22 15:13 ` Avi Kivity [this message]
2012-05-22 15:54 ` Paolo Bonzini
2012-05-23 8:17 ` Stefan Hajnoczi
2012-05-23 8:22 ` Zhi Yong Wu
2012-05-23 8:32 ` Kevin Wolf
2012-05-23 8:43 ` Michael Tokarev
2012-05-23 11:55 ` Stefano Stabellini
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=4FBBAD07.9030106@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.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).