On 07/03/2018 12:51 AM, Markus Armbruster wrote:
Eric Blake writes:
On 07/02/2018 01:48 PM, Markus Armbruster wrote:
Eric Blake writes:
Now that we have useful access to the type name as a comment
in the generated qapi-introspect.c, we don't need to regenerate
code with a temporary -u opti
Eric Blake writes:
> On 07/02/2018 01:48 PM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> Now that we have useful access to the type name as a comment
>>> in the generated qapi-introspect.c, we don't need to regenerate
>>> code with a temporary -u option just to get at type names.
>>>
>
On 07/02/2018 01:48 PM, Markus Armbruster wrote:
Eric Blake writes:
Now that we have useful access to the type name as a comment
in the generated qapi-introspect.c, we don't need to regenerate
code with a temporary -u option just to get at type names.
Signed-off-by: Eric Blake
I occasional
Eric Blake writes:
> Now that we have useful access to the type name as a comment
> in the generated qapi-introspect.c, we don't need to regenerate
> code with a temporary -u option just to get at type names.
>
> Signed-off-by: Eric Blake
I occasionally feed output of query-qmp-schema to ad hoc
On Fri, Jun 29, 2018 at 02:55:44PM -0500, Eric Blake wrote:
> Now that we have useful access to the type name as a comment
> in the generated qapi-introspect.c, we don't need to regenerate
> code with a temporary -u option just to get at type names.
>
> Signed-off-by: Eric Blake
Reviewed-by: Edu
Now that we have useful access to the type name as a comment
in the generated qapi-introspect.c, we don't need to regenerate
code with a temporary -u option just to get at type names.
Signed-off-by: Eric Blake
---
scripts/qapi-gen.py| 5 +
scripts/qapi/introspect.py | 12 ---
