From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Max Carrara <m.carrara@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs 1/2] pveum: add missing roles and privileges
Date: Mon, 17 Jul 2023 16:11:19 +0200 [thread overview]
Message-ID: <d98cd0d8-2eb1-3561-92da-639cf86842a6@proxmox.com> (raw)
In-Reply-To: <20230710151013.2348741-1-m.carrara@proxmox.com>
Am 10/07/2023 um 17:10 schrieb Max Carrara:
> Signed-off-by: Max Carrara <m.carrara@proxmox.com>
> ---
> pveum.adoc | 7 +++++++
> 1 file changed, 7 insertions(+)
>
>
The grouping is a bit odd for a few points, like SDN.Use and Mapping.Use are
roughly about the same thing, but one is at guest level the other at node level.
This might profit from further rework and _maybe_ expansion of categories to
group into, but for now having those privs documented is worth something, so:
applied both patches, thanks!
prev parent reply other threads:[~2023-07-17 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 15:10 [pve-devel] " Max Carrara
2023-07-10 15:10 ` [pve-devel] [PATCH docs 2/2] pveum: sort roles and privileges alphabetically Max Carrara
2023-07-17 14:11 ` 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=d98cd0d8-2eb1-3561-92da-639cf86842a6@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.carrara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.