From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Justin M. Forbes" <jmforbes@linuxtx.org>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Update to 0.15.0 release schedule
Date: Fri, 05 Aug 2011 13:38:19 +0200 [thread overview]
Message-ID: <4E3BD62B.7000607@redhat.com> (raw)
In-Reply-To: <4E3B1155.3010402@codemonkey.ws>
Am 04.08.2011 23:38, schrieb Anthony Liguori:
> Hi,
>
> It took a little longer than I had hoped to converge on a work around
> for the migration issue. -rc2 is out but I don't think 24 hours is
> enough time to get proper testing for the final release.
>
> So I'm pushing 0.15.0 to Monday. Please test and provide feedback.
> Unless there's a brown paper bag bug, -rc2 will be the 0.15.0 release.
You know, there was a reason why I CCed you on the qcow2 corruption fix
with [PATCH 0.15.0] in its subject line...
Though Frediano found another bug in the same function, so the patch
that needs to go into 0.15.0 is now:
[PATCH v3] qcow2: Fix L1 table size after bdrv_snapshot_goto
Kevin
next prev parent reply other threads:[~2011-08-05 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 21:38 [Qemu-devel] Update to 0.15.0 release schedule Anthony Liguori
2011-08-05 11:38 ` Kevin Wolf [this message]
2011-08-05 12:14 ` Anthony Liguori
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=4E3BD62B.7000607@redhat.com \
--to=kwolf@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=jmforbes@linuxtx.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.