From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fabian Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] ui: lvm: better convey space information
Date: Fri, 28 Jan 2022 12:03:43 +0100 [thread overview]
Message-ID: <94f11c8a-cd7a-ac86-2a61-a4e1781acbb7@proxmox.com> (raw)
In-Reply-To: <20220126084202.18781-1-f.ebner@proxmox.com>
On 26.01.22 09:42, Fabian Ebner wrote:
> Namely, that it's just assigned/reserved space, not necessarily
> actively used. Selection of forum threads about this confusion (of
> dozens more):
>
> https://forum.proxmox.com/threads/93820/
> https://forum.proxmox.com/threads/52899/
> https://forum.proxmox.com/threads/52929/
>
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
> www/manager6/node/LVM.js | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2022-01-28 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 8:42 [pve-devel] " Fabian Ebner
2022-01-28 11:03 ` 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=94f11c8a-cd7a-ac86-2a61-a4e1781acbb7@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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