From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC manager/docs] lvm: better expose/explain saferemove option
Date: Thu, 7 Dec 2023 17:10:36 +0100 [thread overview]
Message-ID: <20231207161038.90626-1-f.ebner@proxmox.com> (raw)
Users might not even know that the option or the issue it addresses
exist.
Expose the option in the UI and expand on the "why" in the
documentation.
Motivated by a recent forum post:
https://forum.proxmox.com/threads/137734/
manager:
Fiona Ebner (1):
ui: lvm: expose saferemove setting
www/manager6/storage/LVMEdit.js | 10 ++++++++++
1 file changed, 10 insertions(+)
docs:
Fiona Ebner (1):
storage: lvm: expand on description of saferemove option
pve-storage-lvm.adoc | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.39.2
next reply other threads:[~2023-12-07 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 16:10 Fiona Ebner [this message]
2023-12-07 16:10 ` [pve-devel] [RFC manager 1/1] ui: lvm: expose saferemove setting Fiona Ebner
2024-01-09 9:49 ` Fabian Grünbichler
2023-12-07 16:10 ` [pve-devel] [PATCH docs 1/1] storage: lvm: expand on description of saferemove option Fiona Ebner
2024-01-09 9:38 ` [pve-devel] applied: " Fabian Grünbichler
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=20231207161038.90626-1-f.ebner@proxmox.com \
--to=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