From: Mira Limbeck <m.limbeck@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH common] cert: fix invalid CSR version
Date: Mon, 3 Apr 2023 14:13:38 +0200 [thread overview]
Message-ID: <b3b85329-a931-4b78-5d15-415a576f63bb@proxmox.com> (raw)
In-Reply-To: <20230331161224.1499336-1-m.limbeck@proxmox.com>
Looks like a python-cryptography maintainer opened a pull request on
Github with the exact same change:
https://github.com/proxmox/pve-common/pull/8
next prev parent reply other threads:[~2023-04-03 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 16:12 Mira Limbeck
2023-04-03 12:13 ` Mira Limbeck [this message]
2023-04-20 12:32 ` [pve-devel] applied: " Fabian Grünbichler
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=b3b85329-a931-4b78-5d15-415a576f63bb@proxmox.com \
--to=m.limbeck@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