From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Juan Quintela <quintela@trasno.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Staging tree updated with patches I'm considering for 0.12.0
Date: Fri, 18 Dec 2009 08:20:47 -0600 [thread overview]
Message-ID: <4B2B8FBF.5010003@linux.vnet.ibm.com> (raw)
In-Reply-To: <m3zl5gqz73.fsf@neno.neno>
Juan Quintela wrote:
> Anthony Liguori <aliguori@linux.vnet.ibm.com> wrote:
>
>> I haven't built/tested at all, but this is the set of patches I've
>> collected for the 0.12.0 release. Will be testing tonight and
>> tomorrow and tagging probably around 5pm CST. Will then upload the
>> release and announce once things are propagated.
>>
>> If you have a pending patch that you think should be considered for
>> 0.12.0, please check this tree and let me know if it's not there.
>>
>> http://repo.or.cz/w/qemu/aliguori-queue.git stable-0.12
>>
>
> My fdc changes to ease 0.11 -> 0.12 migration are also missing.
>
> http://patchwork.ozlabs.org/patch/41188/
>
> This one is important because instance_id was changed, and there is no
> way to move from one instance_id to another at migration time.
>
Sorry, there wasn't a FOR 0.12 so it went into the wrong bucket.
--
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-12-18 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 21:53 [Qemu-devel] Staging tree updated with patches I'm considering for 0.12.0 Anthony Liguori
2009-12-18 6:52 ` Markus Armbruster
2009-12-18 14:25 ` Anthony Liguori
2009-12-18 7:30 ` [Qemu-devel] " Jan Kiszka
2009-12-18 14:27 ` Anthony Liguori
2009-12-18 9:04 ` [Qemu-devel] " Gerd Hoffmann
2009-12-18 14:27 ` Anthony Liguori
2009-12-18 9:06 ` Gerd Hoffmann
2009-12-18 11:48 ` Gerd Hoffmann
2009-12-18 14:19 ` Anthony Liguori
[not found] ` <m3zl5gqz73.fsf@neno.neno>
2009-12-18 14:20 ` Anthony Liguori [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=4B2B8FBF.5010003@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.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).