On 09/25/2011 07:36 PM, Blue Swirl wrote:
On Sun, Sep 25, 2011 at 2:10 PM, Avi Kivity<a...@redhat.com> wrote:
> On 09/24/2011 11:05 AM, Blue Swirl wrote:
>>
>> On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori<anth...@codemonkey.ws>
>> wrote:
>> > Consider this a friendly reminder that we're only three weeks away from
>> > the
>> > soft feature freeze for 1.0. I've written a wiki page about my
>> > expectations
>> > for the soft feature freeze. It's inlined here for easier commenting.
>>
>> I think the freezes and the release should be delayed until the memory
>> API conversion is finished, deliberately shipping semi-broken code
>> just to satisfy schedules does not benefit anyone but the schedule
>> creator. It looks to me that converting all buses and devices might be
>> finished by the deadline but it may as well take a bit more until
>> everything works again.
>>
>
> There is a difference between "incomplete conversion" and "semi-broken
> code". Any breakage should be fixed promptly, but after some freeze date
> (not sure if this is the one proposed), additional conversions would be
> pushed to 1.1.
Well, there's PPC VGA which is semi-broken by the incomplete conversion.
Please point out a test case and I'll try to fix it.
--
error compiling committee.c: too many arguments to function
