From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH cluster] pvecm: update comment about updatecerts timeout
Date: Wed, 28 Jun 2023 15:41:54 +0200 [thread overview]
Message-ID: <ec2ccd2a-887d-04fc-1a50-ddbdcc8a2d78@proxmox.com> (raw)
In-Reply-To: <20230628132316.90397-1-f.ebner@proxmox.com>
Am 28/06/2023 um 15:23 schrieb Fiona Ebner:
> The call was moved by 84c3ab0 ("pve-cluster.service: move pvecm call
> to pveproxy.service") to pveproxy.service's ExecStartPre.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> src/PVE/CLI/pvecm.pm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2023-06-28 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 13:23 [pve-devel] " Fiona Ebner
2023-06-28 13:41 ` 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=ec2ccd2a-887d-04fc-1a50-ddbdcc8a2d78@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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