From: Luiz Capitulino <lcapitulino@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Blue Swirl <blauwirbel@gmail.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] Re: [RFT] qemu 0.13.0-rc3
Date: Mon, 11 Oct 2010 20:45:48 -0300 [thread overview]
Message-ID: <20101011204548.16b7bd69@doriath> (raw)
In-Reply-To: <4CB38C82.1090403@linux.vnet.ibm.com>
On Mon, 11 Oct 2010 17:15:30 -0500
Anthony Liguori <aliguori@linux.vnet.ibm.com> wrote:
> After suffering from a prolonged maintainer softlockup, I'm attempting
> to get 0.13.0 release process back on track.
>
> I've tagged qemu-0.13.0-rc3 in git which only carries a few changes
> since 0.13.0-rc1. Most notably, a series of updates from Kevin Wolf and
> Cam Macdonell's ivshmem device.
>
> I think we're pretty good testing wise for the final release but I
> wanted to offer a 24-hour window for last minute fixes. I'm only
> interested in the following:
>
> 1) Patches that are *tested* against the stable-0.13 branch that are
> already committed in master. Please tell me explicitly that you've
> tested the patch and how you've tested it.
>
> 2) Pull requests from other maintainers with cherry-picked patches
> against stable-0.13 that have been tested.
I went through 0.13-rc3's log and found out a number of fixes missing,
some are quite old. Strange, I really thought they were all applied.
Maybe I confused myself when they got applied to master. Not sure.
Anyway, I've cherry-picked them in the following location:
git://repo.or.cz/qemu/qmp-unstable.git for-stable-0.13
Please, note that there non-monitor fixes too.
Alex Williamson (1):
savevm: Reset last block info at beginning of each save
Amit Shah (1):
migration: Accept 'cont' only after successful incoming migration
Eduardo Habkost (1):
disable guest-provided stats on "info balloon" command
Luiz Capitulino (3):
QMP doc: Add 'Stability Considerations' section
QMP: Update README file
QMP/README: Update QMP homepage address
Marcelo Tosatti (1):
set proper migration status on ->write error (v5)
Miguel Di Ciurcio Filho (2):
QMP: update 'query-version' documentation
QMP/monitor: update do_info_version() to output broken down version string
next prev parent reply other threads:[~2010-10-11 23:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 22:15 [Qemu-devel] [RFT] qemu 0.13.0-rc3 Anthony Liguori
2010-10-11 23:45 ` Luiz Capitulino [this message]
2010-10-12 0:02 ` [Qemu-devel] " Anthony Liguori
2010-10-12 15:43 ` [Qemu-devel] " Rick Vernam
2010-10-12 16:27 ` Stefan Weil
2010-10-12 21:34 ` Juergen Lock
2010-10-12 22:00 ` Anthony Liguori
2010-10-13 3:28 ` Juergen Lock
2010-10-13 19:12 ` [Qemu-devel] [PATCH] (master, stable-0.13) zaurus: workaround for io base address rounded down Juergen Lock
2010-10-13 19:45 ` Blue Swirl
2010-10-13 21:30 ` Juergen Lock
2010-10-13 19:24 ` [Qemu-devel] [RFT] qemu 0.13.0-rc3 Juergen Lock
2010-10-13 9:41 ` Amit Shah
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=20101011204548.16b7bd69@doriath \
--to=lcapitulino@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).