From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dietmar Maurer <dietmar@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] upload_custom_certificate api: make key optional
Date: Thu, 18 Jan 2024 16:36:44 +0100 [thread overview]
Message-ID: <f3b6dcc1-1e0f-47ac-b11a-6d0ca020077e@proxmox.com> (raw)
In-Reply-To: <20240118131533.4138518-1-dietmar@proxmox.com>
Am 18/01/2024 um 14:15 schrieb Dietmar Maurer:
> Use existing key if not specified (same as PVE API).
>
> Signed-off-by: Dietmar Maurer <dietmar@proxmox.com>
> ---
> src/api2/node/certificates.rs | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2024-01-18 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 13:15 [pbs-devel] " Dietmar Maurer
2024-01-18 15:36 ` Thomas Lamprecht [this message]
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=f3b6dcc1-1e0f-47ac-b11a-6d0ca020077e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=dietmar@proxmox.com \
--cc=pbs-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