From: Mahmoud Mandour <ma.mandourr@gmail.com>
To: qemu-devel@nongnu.org
Cc: "reviewer:Incompatible changes" <libvir-list@redhat.com>,
Mahmoud Mandour <ma.mandourr@gmail.com>,
cota@braap.org
Subject: [PATCH 9/9] docs/deprecated: deprecate passing plugin args through `arg=`
Date: Fri, 16 Jul 2021 10:03:45 +0200 [thread overview]
Message-ID: <20210716080345.136784-10-ma.mandourr@gmail.com> (raw)
In-Reply-To: <20210716080345.136784-1-ma.mandourr@gmail.com>
Signed-off-by: Mahmoud Mandour <ma.mandourr@gmail.com>
---
docs/system/deprecated.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst
index e2e0090878..aaf0ee5777 100644
--- a/docs/system/deprecated.rst
+++ b/docs/system/deprecated.rst
@@ -126,6 +126,12 @@ other options have been processed. This will either have no effect (if
if they were not given. The property is therefore useless and should not be
specified.
+Plugin argument passing through ``arg=<string>`` (since 6.1)
+''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
+
+Passing arguments through ``arg=`` is redundant is makes the command-line less
+readable, especially when the argument itself consist of a name and a value,
+e.g. ``arg="arg_name=arg_value"``. Therefore, the usage of ``arg`` is redundant.
QEMU Machine Protocol (QMP) commands
------------------------------------
--
2.25.1
next prev parent reply other threads:[~2021-07-16 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 8:03 [PATCH 0/9] new plugin argument passing scheme Mahmoud Mandour
2021-07-16 8:03 ` [PATCH 1/9] plugins: allow plugin arguments to be passed directly Mahmoud Mandour
2021-07-16 8:03 ` [PATCH 2/9] plugins/api: added a boolean parsing plugin api Mahmoud Mandour
2021-07-16 8:03 ` [PATCH 3/9] plugins/hotpages: introduce sortby arg and parsed bool args correctly Mahmoud Mandour
2021-07-16 8:03 ` [PATCH 4/9] plugins/hotblocks: Added correct boolean argument parsing Mahmoud Mandour
2021-07-16 8:03 ` [PATCH 5/9] plugins/lockstep: make socket path not positional & parse bool arg Mahmoud Mandour
2021-07-16 8:03 ` [PATCH 6/9] plugins/hwprofile: adapt to the new plugin arguments scheme Mahmoud Mandour
2021-07-16 8:03 ` [PATCH 7/9] plugins/howvec: Adapting to the new argument passing scheme Mahmoud Mandour
2021-07-16 8:03 ` [PATCH 8/9] docs/tcg-plugins: new passing parameters scheme for cache docs Mahmoud Mandour
2021-07-16 8:03 ` Mahmoud Mandour [this message]
2021-07-16 8:11 ` [PATCH 0/9] new plugin argument passing scheme Mahmoud Mandour
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=20210716080345.136784-10-ma.mandourr@gmail.com \
--to=ma.mandourr@gmail.com \
--cc=cota@braap.org \
--cc=libvir-list@redhat.com \
--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).