diff options
author | Peter Maydell <peter.maydell@linaro.org> | 2020-02-13 17:56:26 +0000 |
---|---|---|
committer | Markus Armbruster <armbru@redhat.com> | 2020-02-15 11:41:50 +0100 |
commit | 26ec4e53f2bf0a381189071f405b99a7e2627a49 (patch) | |
tree | ae7e34e71e3e366c57b8c3112d97970f2d34250a /qapi/transaction.json | |
parent | f56275064e06974b5c03f37ccdb124adbc5baef6 (diff) | |
download | qemu-26ec4e53f2bf0a381189071f405b99a7e2627a49.zip |
qapi: Fix indent level on doc comments in json files
The current doc generation doesn't care much about indentation levels,
but we would like to switch to an rST format, and rST does care about
indentation.
Make the doc comments more strongly consistent about indentation
for multiline constructs like:
@arg: description line 1
description line 2
Returns: line one
line 2
so that there is always exactly one space after the colon, and
subsequent lines align with the first.
This commit is a purely whitespace change, and it does not alter the
generated .texi files (because the texi generation code strips away
all the extra whitespace). This does mean that we end up with some
over-length lines.
Note that when the documentation for an argument fits on a single
line like this:
@arg: one line only
then stray extra spaces after the ':' don't affect the rST output, so
I have not attempted to methodically fix them, though the preference
is a single space here too.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Message-Id: <20200213175647.17628-10-peter.maydell@linaro.org>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
[Commit message tweaked]
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Diffstat (limited to 'qapi/transaction.json')
-rw-r--r-- | qapi/transaction.json | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/qapi/transaction.json b/qapi/transaction.json index 0590dbcd1a..04301f1be7 100644 --- a/qapi/transaction.json +++ b/qapi/transaction.json @@ -132,8 +132,8 @@ # Errors depend on the operations of the transaction # # Note: The transaction aborts on the first failure. Therefore, there will be -# information on only one failed operation returned in an error condition, and -# subsequent actions will not have been attempted. +# information on only one failed operation returned in an error condition, and +# subsequent actions will not have been attempted. # # Since: 1.1 # |