From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christoph Heiss <c.heiss@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager/widget-toolkit 0/2] show altenative interface names in the web ui
Date: Tue, 15 Jul 2025 11:01:21 +0200 [thread overview]
Message-ID: <fa5a2556-c25e-49b5-8e0c-cc0ce9712f04@proxmox.com> (raw)
In-Reply-To: <881f2d84-5f0b-426d-b440-00ce893f68cd@proxmox.com>
Am 15.07.25 um 11:00 schrieb Dominik Csapak:
> btw. tested using
>
> auto nicX
> iface nicY
>
> etc.
>
> it works AFAICT, our parser picks it up as two different ifaces (which makes sense)
> and writes out a seperate 'iface' stanza for nicX in this case the next
> time it's edited... so fine i guess
Alright, thanks for testing and getting back to me with the results!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-15 9:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 10:42 Dominik Csapak
2025-07-14 10:42 ` [pve-devel] [PATCH widget-toolkit 1/1] network: optionally show alternative interface names Dominik Csapak
2025-07-14 10:42 ` [pve-devel] [PATCH pve-manager 1/1] api/ui: show/return " Dominik Csapak
2025-07-14 13:49 ` [pve-devel] [PATCH manager/widget-toolkit 0/2] show altenative interface names in the web ui Christoph Heiss
2025-07-14 13:53 ` Dominik Csapak
2025-07-14 14:31 ` Thomas Lamprecht
2025-07-15 7:41 ` Dominik Csapak
2025-07-15 8:17 ` Thomas Lamprecht
2025-07-15 8:36 ` Dominik Csapak
2025-07-15 8:54 ` Thomas Lamprecht
2025-07-15 9:00 ` Dominik Csapak
2025-07-15 9:01 ` Thomas Lamprecht [this message]
2025-07-15 9:08 ` [pve-devel] superseded: " Dominik Csapak
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=fa5a2556-c25e-49b5-8e0c-cc0ce9712f04@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@proxmox.com \
--cc=d.csapak@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