From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH-SERIES storage/docs/guest-common/qemu-server/common] Improve and unify documentation of bwlimit parameter
Date: Tue, 6 Jun 2023 17:57:05 +0200 [thread overview]
Message-ID: <615f7c88-5674-a869-2fb1-ab1837bc6096@proxmox.com> (raw)
In-Reply-To: <20230329123436.2090248-1-s.hanreich@proxmox.com>
Am 29/03/2023 um 14:34 schrieb Stefan Hanreich:
> While looking through our documentation for the bwlimit parameter
> I noticed that the descriptions are inconsistent and sometimes
> wrong / unclear about the actual unit used for the parameter. This
> patch series fixes some inconsistencies and errors related to this
> parameter.
>
applied series, thanks!
prev parent reply other threads:[~2023-06-06 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 12:34 [pve-devel] " 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 ` [pve-devel] [PATCH qemu-server 1/1] qmrestore: " Stefan Hanreich
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 ` Thomas Lamprecht [this message]
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=615f7c88-5674-a869-2fb1-ab1837bc6096@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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