From: "Thomas Ellmenreich" <t.ellmenreich@proxmox.com>
To: "Christoph Heiss" <c.heiss@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH proxmox/installer 0/2] fix auto-installer/post-hook after schema change
Date: Thu, 10 Sep 2026 16:02:33 +0200 [thread overview]
Message-ID: <DLBOXB3DS91S.1WAWR8492TZG5@proxmox.com> (raw)
In-Reply-To: <20260817125907.878237-1-c.heiss@proxmox.com>
While testing the "add as new remote" series: [1] I had to first
apply these patches for the series I was testing one to
apply cleanly.
[1]: https://lore.proxmox.com/pdm-devel/20260826110504.1339934-1-c.heiss@proxmox.com/
Reviewed-by: Thomas Ellmenreich <t.ellmenreich@proxmox.com>
Tested-by: Thomas Ellmenreich <t.ellmenreich@proxmox.com>
prev parent reply other threads:[~2026-09-10 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 12:54 [PATCH proxmox/installer 0/2] fix auto-installer/post-hook after schema change Christoph Heiss
2026-08-17 12:54 ` [PATCH proxmox 1/2] installer-types: FqdnConfigContainer: implement AsRef into FqdnConfig Christoph Heiss
2026-08-17 12:54 ` [PATCH installer 2/2] auto, post-hook: explicitly ref FqdnConfigContainer when `match`ing Christoph Heiss
2026-09-10 14:02 ` Thomas Ellmenreich [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=DLBOXB3DS91S.1WAWR8492TZG5@proxmox.com \
--to=t.ellmenreich@proxmox.com \
--cc=c.heiss@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