From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com,
Shannon Sterz <s.sterz@proxmox.com>
Subject: [pbs-devel] applied: [RFC PATCH] apt: add keys as option for proxmox repositories
Date: Tue, 15 Jul 2025 23:36:11 +0200 [thread overview]
Message-ID: <175261536812.2426226.8847937955382811455.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250711133917.251291-1-s.sterz@proxmox.com>
On Fri, 11 Jul 2025 15:39:17 +0200, Shannon Sterz wrote:
>
The patch is rather straight forward and simple e2e test seems alright, so:
Applied, thanks!
[1/1] apt: add keys as option for proxmox repositories
commit: 1452499e67746c955d3d117564fbe5d077984bce
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
WARNING: multiple messages have this Message-ID
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com,
Shannon Sterz <s.sterz@proxmox.com>
Subject: [pve-devel] applied: [pbs-devel] [RFC PATCH] apt: add keys as option for proxmox repositories
Date: Tue, 15 Jul 2025 23:36:11 +0200 [thread overview]
Message-ID: <175261536812.2426226.8847937955382811455.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250711133917.251291-1-s.sterz@proxmox.com>
On Fri, 11 Jul 2025 15:39:17 +0200, Shannon Sterz wrote:
>
The patch is rather straight forward and simple e2e test seems alright, so:
Applied, thanks!
[1/1] apt: add keys as option for proxmox repositories
commit: 1452499e67746c955d3d117564fbe5d077984bce
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-15 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 13:39 [pbs-devel] " Shannon Sterz
2025-07-15 21:36 ` Thomas Lamprecht [this message]
2025-07-15 21:36 ` [pve-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=175261536812.2426226.8847937955382811455.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.