From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lukas Wagner <l.wagner@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-guest-common v3 1/1] backup job: remove 'notification-policy' and 'notification-target' options
Date: Fri, 11 Jul 2025 14:34:32 +0200 [thread overview]
Message-ID: <175223726762.2791541.3142175688203579081.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250709081432.91868-1-l.wagner@proxmox.com>
On Wed, 09 Jul 2025 10:14:30 +0200, Lukas Wagner wrote:
> Those were only used in the first iteration of the new notification
> stack, which unfortunately hit pvetest too soon. These two keys have no
> effect and were proactively removed by the GUI when changing
> backup job settings.
>
> With the major update to PVE 9 these can finally be dropped. The pve8to9
> script will gain a check to check for any left-over keys.
>
> [...]
Applied, thanks!
[1/1] backup job: remove 'notification-policy' and 'notification-target' options
(no commit info)
_______________________________________________
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-07-11 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 8:14 [pve-devel] " Lukas Wagner
2025-07-09 8:14 ` [pve-devel] [PATCH manager v3 1/2] ui: remove handling of obsolete notification-policy/target settings Lukas Wagner
2025-07-11 12:34 ` [pve-devel] applied: " Thomas Lamprecht
2025-07-09 8:14 ` [pve-devel] [PATCH manager v3 2/2] ui: backup job details: show notification-mode instead of legacy keys Lukas Wagner
2025-07-11 12:34 ` [pve-devel] applied: " Thomas Lamprecht
2025-07-11 15:04 ` [pve-devel] " Gabriel Goller
2025-07-14 7:26 ` Lukas Wagner
2025-07-14 8:30 ` Gabriel Goller
2025-07-14 8:42 ` Lukas Wagner
2025-07-15 19:59 ` Thomas Lamprecht
2025-07-16 9:11 ` Lukas Wagner
2025-07-11 12:34 ` 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=175223726762.2791541.3142175688203579081.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@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