From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH qemu-server 1/1] qmrestore: improve description of bwlimit parameter
Date: Wed, 29 Mar 2023 14:34:34 +0200 [thread overview]
Message-ID: <20230329123436.2090248-4-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20230329123436.2090248-1-s.hanreich@proxmox.com>
This makes the description consistent with the other places that
have bwlimit as a parameter as well.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
PVE/CLI/qmrestore.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/CLI/qmrestore.pm b/PVE/CLI/qmrestore.pm
index 034233a..a47648b 100755
--- a/PVE/CLI/qmrestore.pm
+++ b/PVE/CLI/qmrestore.pm
@@ -54,7 +54,7 @@ __PACKAGE__->register_method({
description => "Add the VM to the specified pool.",
},
bwlimit => {
- description => "Override i/o bandwidth limit (in KiB/s).",
+ description => "Override I/O bandwidth limit (in KiB/s).",
optional => 1,
type => 'number',
minimum => '0',
--
2.30.2
next prev parent reply other threads:[~2023-03-29 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 12:34 [pve-devel] [PATCH-SERIES storage/docs/guest-common/qemu-server/common] Improve and unify documentation " Stefan Hanreich
2023-03-29 12:34 ` [pve-devel] [PATCH pve-docs 1/1] backup: Fix wrong unit for bandwidth limit Stefan Hanreich
2023-03-29 12:34 ` [pve-devel] [PATCH pve-common 1/1] json schema: improve description of bwlimit parameter Stefan Hanreich
2023-03-29 12:34 ` Stefan Hanreich [this message]
2023-03-29 12:34 ` [pve-devel] [PATCH pve-storage 1/1] volume export: explicitly state unit of bandwidth limit Stefan Hanreich
2023-03-29 12:34 ` [pve-devel] [PATCH pve-guest-common 1/1] vzdump: improve description of bwlimit parameter Stefan Hanreich
2023-06-06 15:57 ` [pve-devel] applied-series: [PATCH-SERIES storage/docs/guest-common/qemu-server/common] Improve and unify documentation " Thomas Lamprecht
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=20230329123436.2090248-4-s.hanreich@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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