From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Jens Meißner" <meissner@b1-systems.de>
Subject: [pve-devel] applied: [PATCH v2] Add DNS challenge schema for knot.
Date: Thu, 18 Nov 2021 11:57:19 +0100 [thread overview]
Message-ID: <ec31ff3c-90b1-3ebe-c05c-2ef032c8fd7d@proxmox.com> (raw)
In-Reply-To: <20211118084934.4493-1-meissner@b1-systems.de>
On 18.11.21 09:49, Jens Meißner wrote:
> Signed-off-by: Jens Meißner <meissner@b1-systems.de>
> ---
> src/dns-challenge-schema.json | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
>
applied, thanks!
Maybe one could open a issue on acme.sh asking regarding the discrepancy
between the documented KNOT_ parameters and the ones actually used in
the code..
prev parent reply other threads:[~2021-11-18 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 8:49 [pve-devel] " Jens Meißner
2021-11-18 10:57 ` 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=ec31ff3c-90b1-3ebe-c05c-2ef032c8fd7d@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=meissner@b1-systems.de \
--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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal