public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] ACK: [RFC proxmox-ve/proxmox-archive-keyring 0/3] split out archive keyring into separate
Date: Thu, 3 Sep 2020 18:28:48 +0200	[thread overview]
Message-ID: <e86ba5f3-e443-3120-d359-74e6e2bb4153@proxmox.com> (raw)
In-Reply-To: <20200806151750.1460435-1-f.gruenbichler@proxmox.com>

On 06.08.20 17:17, Fabian Grünbichler wrote:
> with proxmox-ve as proof of concept - the other meta packages shipping
> keys should be updated in the fashion if we go down this route.
> 

ACK from me, we'll soon-ish start to ship a new key for the bullseye release
next year, would be great if we could do that already in the new repo for
all projects at once.





  parent reply	other threads:[~2020-09-03 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 15:17 [pve-devel] " Fabian Grünbichler
2020-08-06 15:17 ` [pve-devel] [PATCH proxmox-archive-keyring] initial commit Fabian Grünbichler
2020-09-17  9:55   ` [pve-devel] applied: " Thomas Lamprecht
2020-08-06 15:17 ` [pve-devel] [PATCH proxmox-ve 1/2] remove archive keys from proxmox-ve Fabian Grünbichler
2020-08-06 15:17 ` [pve-devel] [PATCH proxmox-ve 2/2] bump version to 6.2-2 Fabian Grünbichler
2020-08-10  9:51 ` [pve-devel] [RFC proxmox-ve/proxmox-archive-keyring 0/3] split out archive keyring into separate Oguz Bektas
2020-09-03 16:28 ` Thomas Lamprecht [this message]
2020-09-17 15:28 ` [pve-devel] applied-series: " 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=e86ba5f3-e443-3120-d359-74e6e2bb4153@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.gruenbichler@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