From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Hannes Laimer <h.laimer@proxmox.com>,
Oguz Bektas <o.bektas@proxmox.com>
Subject: [pve-devel] applied: [PATCH v3 guest-common 2/2] snapshots: delete parent property if new snapshot name is already a parent to existing one
Date: Tue, 30 Nov 2021 08:32:03 +0100 [thread overview]
Message-ID: <b54f138b-7b37-2307-de63-fee46c740e2b@proxmox.com> (raw)
In-Reply-To: <130335e0-4737-5550-c50b-f70bc11eeaf6@proxmox.com>
On 29.11.21 13:31, Hannes Laimer wrote:
> Tested-by: Hannes Laimer <h.laimer@proxmox.com>
>
with above applied, thanks!
prev parent reply other threads:[~2021-11-30 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 9:29 [pve-devel] [PATCH v3 container guest-common 0/2] snapshot parent checks for containers Oguz Bektas
2021-10-14 9:29 ` [pve-devel] [PATCH v3 container 1/2] api: clone_vm: don't include snapshot properties Oguz Bektas
2021-10-14 9:29 ` [pve-devel] [PATCH v3 guest-common 2/2] snapshots: delete parent property if new snapshot name is already a parent to existing one Oguz Bektas
2021-11-04 10:40 ` Oguz Bektas
2021-11-29 12:31 ` Hannes Laimer
2021-11-30 7:32 ` 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=b54f138b-7b37-2307-de63-fee46c740e2b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@proxmox.com \
--cc=o.bektas@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