From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fabian Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server 1/2] restore: write new config to variable first
Date: Tue, 9 Mar 2021 08:05:14 +0100 [thread overview]
Message-ID: <6a5a2126-4306-e746-90de-dbe808f1bb9c@proxmox.com> (raw)
In-Reply-To: <20210308122658.31781-1-f.ebner@proxmox.com>
On 08.03.21 13:26, Fabian Ebner wrote:
> and use file_set_contents to really commit it afterwards. Mostly done as a
> preparation for the later patch for sanitizing the config on restore, but
> shouldn't hurt by itself either.
>
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
> PVE/QemuServer.pm | 83 +++++++++++++++++++++++++----------------------
> 1 file changed, 45 insertions(+), 38 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2021-03-09 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 12:26 [pve-devel] " Fabian Ebner
2021-03-08 12:26 ` [pve-devel] [PATCH qemu-server 2/2] restore: sanitize config for non-root users Fabian Ebner
2021-03-09 7:17 ` Thomas Lamprecht
2021-03-09 10:08 ` Fabian Ebner
2021-03-09 10:15 ` Thomas Lamprecht
2021-03-09 7:05 ` 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=6a5a2126-4306-e746-90de-dbe808f1bb9c@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