From: Oguz Bektas <o.bektas@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 container guest-common 0/2] snapshot parent checks for containers
Date: Wed, 13 Oct 2021 14:31:52 +0200 [thread overview]
Message-ID: <20211013123154.1221852-1-o.bektas@proxmox.com> (raw)
v1->v2:
* remove other snapshot-related properties during clone
* add check when creating new snapshots and abort if new name already a parent for existing snapshot
pve-container:
Oguz Bektas (1):
api: clone_vm: don't include snapshot properties
src/PVE/API2/LXC.pm | 5 +++++
1 file changed, 5 insertions(+)
pve-guest-common:
Oguz Bektas (1):
snapshots: abort if new snapshot name is already parent to existing
one
src/PVE/AbstractConfig.pm | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2021-10-13 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 12:31 Oguz Bektas [this message]
2021-10-13 12:31 ` [pve-devel] [PATCH v2 container 1/2] api: clone_vm: don't include snapshot properties Oguz Bektas
2021-10-14 10:01 ` [pve-devel] applied: " Thomas Lamprecht
2021-10-13 12:31 ` [pve-devel] [PATCH v2 guest-common 2/2] snapshots: abort if new snapshot name is already parent to existing one Oguz Bektas
2021-10-14 7:34 ` Fabian Ebner
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=20211013123154.1221852-1-o.bektas@proxmox.com \
--to=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