Eric Blake writes:
> On 11/18/2015 04:51 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> We already documented that qapi names should match specific
>>> patterns (such as starting with a letter unless it was an enum
>>> value or a downstream extension). Tighten that from a suggestion
On 11/18/2015 04:51 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> We already documented that qapi names should match specific
>> patterns (such as starting with a letter unless it was an enum
>> value or a downstream extension). Tighten that from a suggestion
>> into a hard requirement,
Eric Blake writes:
> We already documented that qapi names should match specific
> patterns (such as starting with a letter unless it was an enum
> value or a downstream extension). Tighten that from a suggestion
> into a hard requirement, which frees up names beginning with a
> single underscor
We already documented that qapi names should match specific
patterns (such as starting with a letter unless it was an enum
value or a downstream extension). Tighten that from a suggestion
into a hard requirement, which frees up names beginning with a
single underscore for qapi internal usage. Als
