From: Blue Swirl <blauwirbel@gmail.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Artyom Tarasenko <atar4qemu@googlemail.com>
Subject: Re: [Qemu-devel] [ANNOUNCE][Call-For-Testing] Release 0.12.0-rc1 of QEMU
Date: Mon, 14 Dec 2009 16:56:09 +0000 [thread overview]
Message-ID: <f43fc5580912140856l6254f628rc4be35a4532dfe7d@mail.gmail.com> (raw)
In-Reply-To: <4B2665E2.9070603@linux.vnet.ibm.com>
On Mon, Dec 14, 2009 at 4:20 PM, Anthony Liguori
<aliguori@linux.vnet.ibm.com> wrote:
> Artyom Tarasenko wrote:
>>
>> 2009/12/14 Anthony Liguori <aliguori@linux.vnet.ibm.com>:
>>
>>>
>>> The current plan is to release 0.12.0 on Friday, Dec 18th. Depending on
>>> the
>>> severity of bug fixes we get between now and then, we may do another
>>> release
>>> candidate in the middle of the week.
>>>
>>
>> I see that the carry flag fix for sparc is included. Are you planning
>> to include the rest of my sparc/scsi patches? They are not as drastic
>> as the carry fix, so they shouldn't break something which isn't
>> already broken. On the other hand, the ability to boot Solaris/sparc
>> kernel may be important for some users.
>>
>
> It's up to Blue Swirl to decide about the sparc patches. The SCSI Inquiry
> fix is reasonable but it missed the -rc2 deadline. I'll queue it for final
> release.
The FDC fix should be OK. Technically AFX patch adds new
functionality, but very limited.
next prev parent reply other threads:[~2009-12-14 16:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 14:06 [Qemu-devel] [ANNOUNCE][Call-For-Testing] Release 0.12.0-rc1 of QEMU Anthony Liguori
2009-12-14 16:08 ` Artyom Tarasenko
2009-12-14 16:20 ` Anthony Liguori
2009-12-14 16:56 ` Blue Swirl [this message]
2009-12-14 17:00 ` Avi Kivity
2009-12-14 17:28 ` Anthony Liguori
2009-12-16 3:19 ` Ryan Harper
-- strict thread matches above, loose matches on Subject: below --
2009-12-06 22:43 Anthony Liguori
2009-12-07 12:49 ` Luiz Capitulino
2009-12-07 13:45 ` Anthony Liguori
2009-12-07 13:59 ` Luiz Capitulino
2009-12-07 18:34 ` Daniel P. Berrange
2009-12-07 19:43 ` Anthony Liguori
2009-12-07 20:25 ` Daniel P. Berrange
2009-12-08 10:40 ` Gerd Hoffmann
2009-12-08 10:52 ` Daniel P. Berrange
2009-12-08 12:52 ` Gerd Hoffmann
2009-12-08 13:07 ` Gerd Hoffmann
2009-12-09 10:21 ` Daniel P. Berrange
2009-12-09 10:27 ` Ian Molton
2009-12-09 16:56 ` Daniel P. Berrange
2009-12-10 9:22 ` Gerd Hoffmann
2009-12-10 12:16 ` Daniel P. Berrange
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=f43fc5580912140856l6254f628rc4be35a4532dfe7d@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=atar4qemu@googlemail.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).