From: Jeong JungGyu via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Jeong JungGyu <angrystar170@gmail.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: [pve-devel] SPAM: [PATCH] bump version to 9.0.0~22
Date: Fri, 12 Sep 2025 17:05:16 +0900 [thread overview]
Message-ID: <mailman.480.1757664423.418.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 4239 bytes --]
From: Jeong JungGyu <angrystar170@gmail.com>
To: pve-devel@lists.proxmox.com
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>, Jeong JungGyu <angrystar170@gmail.com>
Subject: SPAM: [PATCH] bump version to 9.0.0~22
Date: Fri, 12 Sep 2025 17:05:16 +0900
Message-ID: <20250912080626.1692668-3-angrystar170@gmail.com>
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Signed-off-by: Jeong JungGyu <angrystar170@gmail.com>
---
debian/changelog | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index b3722db0..c7cbfe00 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pve-manager (9.0.0~22) trixie; urgency=medium
+
+ * sync over 8 to 9 upgrade checks from stable-8 branch.
+
+ * api: backup: remove unneeded call of rrd_dump method.
+
+ -- Proxmox Support Team <support@proxmox.com> Mon, 04 Aug 2025 21:43:25 +0200
+
pve-manager (9.0.0~21) trixie; urgency=medium
* ui: migration pre-conditions: make lack of support for conntrack state
--
2.43.0
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-09-12 8:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.480.1757664423.418.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=angrystar170@gmail.com \
--cc=t.lamprecht@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