From: "Thomas Ellmenreich" <t.ellmenreich@proxmox.com>
To: "Thomas Ellmenreich" <t.ellmenreich@proxmox.com>,
<pve-devel@lists.proxmox.com>
Subject: superseded: [PATCH pve-docs 1/1] network/sdn: update and clean up vlan information
Date: Tue, 20 Oct 2026 08:48:13 +0200 [thread overview]
Message-ID: <DM9GQJTE7AZH.3U23QHRC018QR@proxmox.com> (raw)
In-Reply-To: <20261001130839.203329-1-t.ellmenreich@proxmox.com>
Superseded-by:
https://lore.proxmox.com/pve-devel/20261020064508.32479-1-t.ellmenreich@proxmox.com/T/#u
prev parent reply other threads:[~2026-10-20 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:08 [PATCH pve-docs 1/1] network/sdn: update and clean up vlan information Thomas Ellmenreich
2026-10-01 15:14 ` Stefan Hanreich
2026-10-02 12:32 ` Thomas Ellmenreich
2026-10-09 9:51 ` Stefan Hanreich
2026-10-20 6:48 ` Thomas Ellmenreich [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=DM9GQJTE7AZH.3U23QHRC018QR@proxmox.com \
--to=t.ellmenreich@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