From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Dominik Csapak <d.csapak@proxmox.com>
Subject: applied: [PATCH proxmox-backup v2] ui: always use arrays for 'delete' property
Date: Fri, 3 Jul 2026 00:32:58 +0200 [thread overview]
Message-ID: <178303157654.3972458.6614047372316727040.b4-ty@b4> (raw)
In-Reply-To: <20260629130818.1369588-1-d.csapak@proxmox.com>
On Mon, 29 Jun 2026 15:07:24 +0200, Dominik Csapak wrote:
> In PBS we always expect an array for deletable properties, never a
> comma-separated string. The code that does this was carried over from
> PVE where we often use those.
>
> Instead of working around in every place where we use delete_if_default,
> simply use a different implementation.
>
> [...]
Applied, thanks!
[1/1] ui: always use arrays for 'delete' property
commit: 6d515b2625d235360199f299da0cfff68f240c86
prev parent reply other threads:[~2026-07-02 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 13:07 [PATCH proxmox-backup v2] ui: always use arrays for 'delete' property Dominik Csapak
2026-07-02 22:32 ` 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=178303157654.3972458.6614047372316727040.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-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