From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-manager v2 1/1] api/ui: show/return alternative interface names
Date: Thu, 17 Jul 2025 18:00:15 +0200 [thread overview]
Message-ID: <175276796108.4120414.8064689309929887654.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250715090749.1608768-3-d.csapak@proxmox.com>
On Tue, 15 Jul 2025 11:07:49 +0200, Dominik Csapak wrote:
> in api listing for all interfaces, and in the GET call for an individual
> interface.
>
> For intefaces that are already using an 'altname' in the iface stanza,
> we look up the 'legacy' interface name and the remaining altnames and
> show those.
>
> [...]
Applied, thanks!
[1/1] api/ui: show/return alternative interface names
_______________________________________________
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-17 16:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 9:07 [pve-devel] [PATCH manager/widget-toolkit v2 0/2] show altenative interface names in the web ui Dominik Csapak
2025-07-15 9:07 ` [pve-devel] [PATCH widget-toolkit v2 1/1] network: optionally show alternative interface names Dominik Csapak
2025-07-15 19:56 ` Thomas Lamprecht
2025-07-16 22:47 ` Thomas Lamprecht
2025-07-15 9:07 ` [pve-devel] [PATCH pve-manager v2 1/1] api/ui: show/return " Dominik Csapak
2025-07-15 9:21 ` Stefan Hanreich
2025-07-15 9:30 ` Dominik Csapak
2025-07-15 9:41 ` Stefan Hanreich
2025-07-15 10:33 ` Dominik Csapak
2025-07-15 11:06 ` Stefan Hanreich
2025-07-15 12:36 ` Thomas Lamprecht
2025-07-15 13:08 ` Stefan Hanreich
2025-07-15 13:15 ` Thomas Lamprecht
2025-07-15 13:47 ` Stefan Hanreich
2025-07-17 16:00 ` 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=175276796108.4120414.8064689309929887654.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-devel@lists.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