From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH-SERIES v2 guest-common] replication improvements
Date: Thu, 11 Apr 2024 13:58:40 +0200 [thread overview]
Message-ID: <afec822e-6858-4a8a-bb07-554b27be6a90@proxmox.com> (raw)
In-Reply-To: <20231213141747.679613-1-f.ebner@proxmox.com>
Am 13.12.23 um 15:17 schrieb Fiona Ebner:
> Improve error when finding a common base snapshot and fix the check if
> a snapshot is needed by replication when there are volumes with
> replicate setting turned off.
>
> First version:
> https://lists.proxmox.com/pipermail/pve-devel/2023-January/055513.html
>
> Changes since v1:
> * add an additional fix
>
> Fiona Ebner (3):
> replication: prepare: include volumes without snapshots in the result
> replication: find common base: improve error when no common base
> snapshot exists
> abstract config: fix snapshot needed by replication check
>
> src/PVE/AbstractConfig.pm | 2 +-
> src/PVE/Replication.pm | 17 ++++++++++++-----
> 2 files changed, 13 insertions(+), 6 deletions(-)
>
Ping
next prev parent reply other threads:[~2024-04-11 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 14:17 Fiona Ebner
2023-12-13 14:17 ` [pve-devel] [PATCH v2 guest-common 1/3] replication: prepare: include volumes without snapshots in the result Fiona Ebner
2023-12-13 14:17 ` [pve-devel] [PATCH v2 guest-common 2/3] replication: find common base: improve error when no common base snapshot exists Fiona Ebner
2023-12-13 14:17 ` [pve-devel] [PATCH v2 guest-common 3/3] abstract config: fix snapshot needed by replication check Fiona Ebner
2024-04-11 11:58 ` Fiona Ebner [this message]
2024-04-11 16:18 ` [pve-devel] applied-series: [PATCH-SERIES v2 guest-common] replication improvements 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=afec822e-6858-4a8a-bb07-554b27be6a90@proxmox.com \
--to=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