From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com, Nicolas Frey <n.frey@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH pve-access-control 0/2] api: token: fix #6890: allow comment removal via delete parameter or empty string
Date: Fri, 14 Nov 2025 10:53:48 +0100 [thread overview]
Message-ID: <176311400550.232865.17451599102701663109.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251008111930.55867-1-n.frey@proxmox.com>
On Wed, 08 Oct 2025 13:19:18 +0200, Nicolas Frey wrote:
> this patch series fixes #6890, which reported that removal of the
> comment property on tokens was not possible. Also adds a delete param
> which behaves the same as if the comment was set to an empty string.
>
> Nicolas Frey (2):
> api: token: fix #6890: add ability to remove comment with empty string
> api: token: add delete parameter for comment
>
> [...]
Applied, thanks!
[1/2] api: token: fix #6890: add ability to remove comment with empty string
commit: 5845e4094f59191b2bf5cceabe620f4ab3ab3ecd
[2/2] api: token: add delete parameter for comment
commit: 73652d3e7b1fd87c386cc1b0cd4edc8467f04b32
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-11-14 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 11:19 [pve-devel] " Nicolas Frey
2025-10-08 11:19 ` [pve-devel] [PATCH pve-access-control 1/2] api: token: fix #6890: add ability to remove comment with " Nicolas Frey
2025-10-08 11:19 ` [pve-devel] [PATCH pve-access-control 2/2] api: token: add delete parameter for comment Nicolas Frey
2025-11-14 9:53 ` Fabian Grünbichler [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=176311400550.232865.17451599102701663109.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=n.frey@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.