From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-manager 0/3] wireguard fabric node ui touch-ups
Date: Mon, 18 May 2026 17:07:44 +0200 [thread overview]
Message-ID: <20260518150747.103342-1-h.laimer@proxmox.com> (raw)
Small improvemnts to the wireguard node edit dialog, don't really depend
on eachother.
Hannes Laimer (3):
ui: sdn: improve wireguard node edit dialog with no interfaces
ui: sdn: avoid flicker when opening wireguard dialogs
ui: sdn: skip delete confirmation for unsaved wireguard interfaces
.../sdn/fabrics/wireguard/InterfacePanel.js | 65 +++++++++++++++----
.../sdn/fabrics/wireguard/NodeEdit.js | 2 +
2 files changed, 53 insertions(+), 14 deletions(-)
--
2.47.3
next reply other threads:[~2026-05-18 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 15:07 Hannes Laimer [this message]
2026-05-18 15:07 ` [PATCH pve-manager 1/3] ui: sdn: improve wireguard node edit dialog with no interfaces Hannes Laimer
2026-05-18 15:07 ` [PATCH pve-manager 2/3] ui: sdn: avoid flicker when opening wireguard dialogs Hannes Laimer
2026-05-18 15:07 ` [PATCH pve-manager 3/3] ui: sdn: skip delete confirmation for unsaved wireguard interfaces Hannes Laimer
2026-05-18 20:06 ` applied: [PATCH pve-manager 0/3] wireguard fabric node ui touch-ups Thomas Lamprecht
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=20260518150747.103342-1-h.laimer@proxmox.com \
--to=h.laimer@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