From: Fiona Ebner <f.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 cluster 1/4] setup: split generation of local (i.e. non-pmxcfs) files out into helper
Date: Wed, 30 Aug 2023 15:10:43 +0200 [thread overview]
Message-ID: <eefdbef4-4737-f774-98bc-6424efd34a16@proxmox.com> (raw)
In-Reply-To: <73156357-8e7c-4e45-b8b7-5de33605f692@proxmox.com>
Am 30.08.23 um 11:37 schrieb Thomas Lamprecht:
> Am 30/08/2023 um 11:14 schrieb Fiona Ebner:
>> Ping for the series
>
> I already applied all but 3/4 "pvecm: updatecerts: silence warning that
> potentially has no contex" one, which was replaced by
>
>
> https://git.proxmox.com/?p=pve-common.git;a=commitdiff;h=a6aa0ae9453190e029dad43dfe3d19e830c1543a
Sent fixes for this one, because I think it ignores a bit too much now.
> and
> https://git.proxmox.com/?p=pve-cluster.git;a=commitdiff;h=66b0e690fec93c63952645213cc3110df3d56162
>
> I seemingly forgot to reply here, sorry. Can you please recheck if nothing
> was missed?
>
Thanks! This is certainly better then the manual filter I proposed. The
rest looks fine to me :)
prev parent reply other threads:[~2023-08-30 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 11:59 Fiona Ebner
2023-06-30 11:59 ` [pve-devel] [PATCH v3 cluster 2/4] pvecm: updatecerts: wait for quorum Fiona Ebner
2023-06-30 11:59 ` [pve-devel] [PATCH v3 cluster 3/4] pvecm: updatecerts: silence warning that potentially has no context Fiona Ebner
2023-06-30 11:59 ` [pve-devel] [PATCH v3 cluster 4/4] fix typo Fiona Ebner
2023-08-30 9:14 ` [pve-devel] [PATCH v3 cluster 1/4] setup: split generation of local (i.e. non-pmxcfs) files out into helper Fiona Ebner
2023-08-30 9:37 ` Thomas Lamprecht
2023-08-30 13:10 ` Fiona Ebner [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=eefdbef4-4737-f774-98bc-6424efd34a16@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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.