From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH container 2/2] restore: add more informational messages
Date: Tue, 26 Jan 2021 18:53:09 +0100 [thread overview]
Message-ID: <03c25559-14f9-168e-5906-2f8b87a5003b@proxmox.com> (raw)
In-Reply-To: <20201125140750.2851534-2-f.gruenbichler@proxmox.com>
On 25.11.20 15:07, Fabian Grünbichler wrote:
> to provide context for warnings/output created by various sub-operations.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
> src/PVE/API2/LXC.pm | 5 +++++
> 1 file changed, 5 insertions(+)
>
>
applied, thanks!
next prev parent reply other threads:[~2021-01-26 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 14:07 [pve-devel] [PATCH container 1/2] restore: pass target vmid to config recovery Fabian Grünbichler
2020-11-25 14:07 ` [pve-devel] [PATCH container 2/2] restore: add more informational messages Fabian Grünbichler
2021-01-26 17:53 ` Thomas Lamprecht [this message]
2021-01-26 17:52 ` [pve-devel] applied: [PATCH container 1/2] restore: pass target vmid to config recovery Thomas Lamprecht
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=03c25559-14f9-168e-5906-2f8b87a5003b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@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