"Covers only syntactic aspects of QMP" was initially accurate, but we we neglected to update it when we added @insecure-types. Do that now.
While there, move the limitation notes below the enum value descriptions to avoid forward references, and mark up an existing reference properly. Signed-off-by: Markus Armbruster <[email protected]> --- qapi/compat.json | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/qapi/compat.json b/qapi/compat.json index f6bc93904f..d1fb74abf7 100644 --- a/qapi/compat.json +++ b/qapi/compat.json @@ -57,13 +57,6 @@ # # This is intended for testing users of the management interfaces. # -# Limitation: covers only syntactic aspects of QMP, i.e. stuff tagged -# with feature 'deprecated' or 'unstable'. We may want to extend it -# to cover semantic aspects and CLI. -# -# Limitation: deprecated-output policy @hide is not implemented for -# enumeration values. They behave the same as with policy @accept. -# # @deprecated-input: how to handle deprecated input (default 'accept') # # @deprecated-output: how to handle deprecated output (default @@ -78,6 +71,14 @@ # @insecure-types: how to handle types that are not declared secure # (default 'accept') (since 11.2) # +# Limitation: @deprecated-input, @deprecated-output, @unstable-input, +# and @unstable-output cover only syntactic aspects of QMP, i.e. stuff +# tagged with feature 'deprecated' or 'unstable'. We may want to +# extend it to cover semantic aspects and CLI. +# +# Limitation: @deprecated-output policy @hide is not implemented for +# enumeration values. They behave the same as with policy @accept. +# # Since: 6.0 ## { 'struct': 'CompatPolicy', -- 2.55.0
