From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC PATCH ifupdown2 7/7] bump version to 3.9.0-1+pmx2
Date: Wed, 23 Apr 2025 12:45:36 +0200 [thread overview]
Message-ID: <20250423104556.644234-8-c.heiss@proxmox.com> (raw)
In-Reply-To: <20250423104556.644234-1-c.heiss@proxmox.com>
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
debian/changelog | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 53c781d..584b410 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+ifupdown2 (3.9.0-1+pmx2) bookworm; urgency=medium
+
+ * add patch for IPv6 vxlan-local-tunnelip support
+
+ -- Proxmox Support Team <support@proxmox.com> Tue, 22 Apr 2025 12:45:30 +0200
+
ifupdown2 (3.9.0-1+pmx1) bookworm; urgency=medium
* update to 3.9.0 upstream release
--
2.49.0
_______________________________________________
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-04-23 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 10:45 [pve-devel] [PATCH ifupdown2 0/7] bump to upstream 3.9.0 release Christoph Heiss
2025-04-23 10:45 ` [pve-devel] [PATCH ifupdown2 1/7] gitignore: add dpkg build artifacts Christoph Heiss
2025-04-23 10:45 ` [pve-devel] [PATCH ifupdown2 2/7] update submodule to 3.9.0 Christoph Heiss
2025-04-23 10:45 ` [pve-devel] [PATCH ifupdown2 3/7] d/changelog: merge in upstream changelog Christoph Heiss
2025-04-23 10:45 ` [pve-devel] [PATCH ifupdown2 4/7] d/patches: revert broken bridge-fd `validrange` clamping Christoph Heiss
2025-04-23 10:45 ` [pve-devel] [PATCH ifupdown2 5/7] bump version to 3.9.0-1+pmx1 Christoph Heiss
2025-04-23 10:45 ` [pve-devel] [RFC PATCH ifupdown2 6/7] d/patches: add patch for adding IPv6 vxlan-local-tunnelip Christoph Heiss
2025-04-23 10:45 ` Christoph Heiss [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=20250423104556.644234-8-c.heiss@proxmox.com \
--to=c.heiss@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal