From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Konstantin Kostiuk <kkostiuk@redhat.com>
Subject: [PULL 5/5] qga/qapi-schema: Move command description right after command name
Date: Sat, 3 Feb 2024 09:34:15 +0100 [thread overview]
Message-ID: <20240203083415.2937003-6-armbru@redhat.com> (raw)
In-Reply-To: <20240203083415.2937003-1-armbru@redhat.com>
Documentation of commands guest-ssh-get-authorized-keys,
guest-ssh-add-authorized-keys, and guest-ssh-remove-authorized-keys
describes the command's purpose after its arguments. Everywhere else,
we do it the other way round. Move it for consistency.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20240129115008.674248-6-armbru@redhat.com>
Reviewed-by: Konstantin Kostiuk <kkostiuk@redhat.com>
---
qga/qapi-schema.json | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/qga/qapi-schema.json b/qga/qapi-schema.json
index 876e2a8ea8..50b0a558c7 100644
--- a/qga/qapi-schema.json
+++ b/qga/qapi-schema.json
@@ -1565,11 +1565,11 @@
##
# @guest-ssh-get-authorized-keys:
#
-# @username: the user account to add the authorized keys
-#
# Return the public keys from user .ssh/authorized_keys on Unix
# systems (not implemented for other systems).
#
+# @username: the user account to add the authorized keys
+#
# Returns: @GuestAuthorizedKeys
#
# Since: 5.2
@@ -1582,6 +1582,9 @@
##
# @guest-ssh-add-authorized-keys:
#
+# Append public keys to user .ssh/authorized_keys on Unix systems (not
+# implemented for other systems).
+#
# @username: the user account to add the authorized keys
#
# @keys: the public keys to add (in OpenSSH/sshd(8) authorized_keys
@@ -1589,9 +1592,6 @@
#
# @reset: ignore the existing content, set it with the given keys only
#
-# Append public keys to user .ssh/authorized_keys on Unix systems (not
-# implemented for other systems).
-#
# Returns: Nothing on success.
#
# Since: 5.2
@@ -1603,15 +1603,15 @@
##
# @guest-ssh-remove-authorized-keys:
#
+# Remove public keys from the user .ssh/authorized_keys on Unix
+# systems (not implemented for other systems). It's not an error if
+# the key is already missing.
+#
# @username: the user account to remove the authorized keys
#
# @keys: the public keys to remove (in OpenSSH/sshd(8) authorized_keys
# format)
#
-# Remove public keys from the user .ssh/authorized_keys on Unix
-# systems (not implemented for other systems). It's not an error if
-# the key is already missing.
-#
# Returns: Nothing on success.
#
# Since: 5.2
--
2.43.0
next prev parent reply other threads:[~2024-02-03 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 8:34 [PULL 0/5] QAPI patches patches for 2024-02-03 Markus Armbruster
2024-02-03 8:34 ` [PULL 1/5] qapi: Drop redundant documentation of inherited members Markus Armbruster
2024-02-03 8:34 ` [PULL 2/5] qapi: Drop redundant documentation of conditional Markus Armbruster
2024-02-03 8:34 ` [PULL 3/5] qapi: Elide "Potential additional modes" from generated docs Markus Armbruster
2024-02-03 8:34 ` [PULL 4/5] qga: Move type description right after type name Markus Armbruster
2024-02-03 8:34 ` Markus Armbruster [this message]
2024-02-03 16:27 ` [PULL 0/5] QAPI patches patches for 2024-02-03 Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240203083415.2937003-6-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).