From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager v3 1/1] qemu: network: adjust MTU emptyText to match new default behavior
Date: Thu, 17 Jul 2025 20:39:43 +0200 [thread overview]
Message-ID: <175277758217.14406.1116665665093846755.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250717175012.606372-3-s.hanreich@proxmox.com>
On Thu, 17 Jul 2025 19:50:11 +0200, Stefan Hanreich wrote:
> Leaving the MTU field unset now defaults to the bridge MTU, rather
> than 1500. Reflect this change by indicating the new behavior in the
> emptyText of the MTU field. While we're at it, add a gettext call so
> it can be translated. I've taken the same text as from the container
> dialogue, so it should already use existing translations.
>
>
> [...]
Applied, thanks!
[1/1] qemu: network: adjust MTU emptyText to match new default behavior
_______________________________________________
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-17 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 17:50 [pve-devel] [PATCH docs/manager/qemu-server v3 0/3] Make VirtIO network devices inherit MTU from bridge by default Stefan Hanreich
2025-07-17 17:50 ` [pve-devel] [PATCH qemu-server v3 1/1] net: automatically set host_mtu to bridge mtu for virtio netdevs Stefan Hanreich
2025-07-17 18:39 ` Thomas Lamprecht
2025-07-17 17:50 ` [pve-devel] [PATCH pve-manager v3 1/1] qemu: network: adjust MTU emptyText to match new default behavior Stefan Hanreich
2025-07-17 18:39 ` Thomas Lamprecht [this message]
2025-07-17 17:50 ` [pve-devel] [PATCH pve-docs v3 1/1] qm: document new default behavior for mtu setting Stefan Hanreich
2025-07-17 18:39 ` 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=175277758217.14406.1116665665093846755.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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