From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, pdm-devel@lists.proxmox.com,
Shannon Sterz <s.sterz@proxmox.com>
Subject: [pdm-devel] applied: [PATCH proxmox-backup v2 1/2] pbs3to4: move pbs3to4 to common proxmox-upgrade-checks crate
Date: Sun, 30 Nov 2025 21:19:43 +0100 [thread overview]
Message-ID: <176453395287.2229823.5087425172890631908.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251124103444.117406-4-s.sterz@proxmox.com>
On Mon, 24 Nov 2025 11:34:43 +0100, Shannon Sterz wrote:
>
Applied, with the new build-dependency and some more context for why we can
remove 2to3 fleeced in, thanks!
[1/2] pbs3to4: move pbs3to4 to common proxmox-upgrade-checks crate
commit: 86436722b507f4c32257c9737d56783a8d42f909
[2/2] pbs2to3: remove now unused script
commit: 9f88a0211d130c7728d9010aaa1fcf91a7e9f764
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next prev parent reply other threads:[~2025-11-30 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 10:34 [pdm-devel] [PATCH datacenter-manager/proxmox{, -backup} v2 0/4] move upgrade checks to a common crate under proxmox-rs Shannon Sterz
2025-11-24 10:34 ` [pdm-devel] [PATCH proxmox v2 1/1] upgrade-checks: fix meta package version check Shannon Sterz
2025-11-30 20:05 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-24 10:34 ` [pdm-devel] [PATCH proxmox-backup v2 1/2] pbs3to4: move pbs3to4 to common proxmox-upgrade-checks crate Shannon Sterz
2025-11-30 20:19 ` Thomas Lamprecht [this message]
2025-11-24 10:34 ` [pdm-devel] [PATCH proxmox-backup v2 2/2] pbs2to3: remove now unused script Shannon Sterz
2025-11-24 10:34 ` [pdm-devel] [PATCH datacenter-manager v2 1/1] upgrade-checks: use common proxmox-upgrade-checks crate Shannon Sterz
2025-12-01 2:55 ` [pdm-devel] applied: " 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=176453395287.2229823.5087425172890631908.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
--cc=s.sterz@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