qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v10 00/30] qapi member collision (post-introspec


From: Markus Armbruster
Subject: Re: [Qemu-devel] [PATCH v10 00/30] qapi member collision (post-introspection cleanups, subset C')
Date: Tue, 10 Nov 2015 12:57:54 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Markus Armbruster <address@hidden> writes:

> Eric Blake <address@hidden> writes:
>
>> On 11/09/2015 02:59 AM, Markus Armbruster wrote:
>>> Eric Blake <address@hidden> writes:
>>> 
>>>> On 11/06/2015 09:03 AM, Markus Armbruster wrote:
>>>>> Eric Blake <address@hidden> writes:
>>> [...]
>>>>>> Hopefully, we are converging on something that will be ready
>>>>>> for a pull request, especially for the earlier patches of this
>>>>>> subset.
>>>>>
>>>>> I guess you mean PATCH 01-12.  I had a few questions, but the most
>>>>> likely outcome seems to be minor touchups I could apply in my tree.
>>>>>
>>>>> I'm okay with trying to get more patches in, but let's get these out of
>>>>> the way meanwhile.
>>>>
>>>> Yes, 01-12 seems like a good first set, if you want to make those
>>>> touchups (I've supplied some potential text improvements in reply to
>>>> some of your comments); I'm happy, as always, to take a peek over your
>>>> staging repo to double check what you are prepping for the pull request.
>>> 
>>> Please have a look at my qapi-next branch.
>>
>> Close, but commit 5f72bb85 on that branch is missing the one-line summary:
>>
>> qapi: Simplify error cleanup in test-qmp-*
>
> Fixed & sent pull request, thanks!

Pulled.

I think I'll close the QAPI floodgates for 2.5 now.  Bug fixes are of
course exempted, and if we find something that impacts ABI, I'm willing
to consider patches.  Work on our backlog can continue uninterrupted;
I'm happy to collect patches that are ready, and will take care of
getting them into master once 2.6 opens.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]