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] applied: Re: [PATCH proxmox-archive-keyring] initial commit
Date: Thu, 17 Sep 2020 11:55:45 +0200 [thread overview]
Message-ID: <daaacbd3-11ee-8f45-e7c7-68176dfea385@proxmox.com> (raw)
In-Reply-To: <20200806151750.1460435-2-f.gruenbichler@proxmox.com>
On 8/6/20 5:17 PM, Fabian Grünbichler wrote:
> taking over from product-specific meta packages, which can now depend on
> proxmox-archive-keyring and drop their copies of the keys.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
> note: new repo ;)
>
> Makefile | 31 +++++++++++++++++++++++++
> debian/changelog | 5 ++++
> debian/compat | 1 +
> debian/control | 12 ++++++++++
> debian/copyright | 21 +++++++++++++++++
> debian/proxmox-archive-keyring.docs | 1 +
> debian/proxmox-archive-keyring.install | 2 ++
> debian/proxmox-release-buster.gpg | Bin 0 -> 1202 bytes
> debian/proxmox-release-stretch.gpg | Bin 0 -> 1181 bytes
> debian/rules | 28 ++++++++++++++++++++++
> 10 files changed, 101 insertions(+)
> create mode 100644 Makefile
> create mode 100644 debian/changelog
> create mode 100644 debian/compat
> create mode 100644 debian/control
> create mode 100644 debian/copyright
> create mode 100644 debian/proxmox-archive-keyring.docs
> create mode 100644 debian/proxmox-archive-keyring.install
> create mode 100644 debian/proxmox-release-buster.gpg
> create mode 100644 debian/proxmox-release-stretch.gpg
> create mode 100755 debian/rules
>
>
applied, thanks!
next prev parent reply other threads:[~2020-09-17 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 15:17 [pve-devel] [RFC proxmox-ve/proxmox-archive-keyring 0/3] split out archive keyring into separate Fabian Grünbichler
2020-08-06 15:17 ` [pve-devel] [PATCH proxmox-archive-keyring] initial commit Fabian Grünbichler
2020-09-17 9:55 ` Thomas Lamprecht [this message]
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 ` [pve-devel] ACK: " Thomas Lamprecht
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=daaacbd3-11ee-8f45-e7c7-68176dfea385@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