From: "Thomas Ellmenreich" <t.ellmenreich@proxmox.com>
To: "Thomas Ellmenreich" <t.ellmenreich@proxmox.com>,
<pve-devel@lists.proxmox.com>
Subject: superseded: [PATCH pve-docs v2 1/1] network/sdn: update and clean up VLAN information
Date: Mon, 02 Nov 2026 12:57:22 +0100 [thread overview]
Message-ID: <DMKPGBXQ7IRY.21RI7YH9VUX4E@proxmox.com> (raw)
In-Reply-To: <20261020064508.32479-1-t.ellmenreich@proxmox.com>
Superseded-by: https://lore.proxmox.com/all/20261102115536.232711-1-t.ellmenreich@proxmox.com/T/#u
prev parent reply other threads:[~2026-11-02 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 6:45 [PATCH pve-docs v2 1/1] network/sdn: update and clean up VLAN information Thomas Ellmenreich
2026-10-20 9:16 ` Michael Köppl
2026-10-20 13:54 ` Stefan Hanreich
2026-10-21 7:28 ` Thomas Ellmenreich
2026-10-27 10:33 ` Stefan Hanreich
2026-11-02 11:57 ` 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=DMKPGBXQ7IRY.21RI7YH9VUX4E@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