From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES] unify vzdump exclude-path behavior
Date: Fri, 20 Nov 2020 15:50:40 +0100 [thread overview]
Message-ID: <20201120145045.31543-1-f.ebner@proxmox.com> (raw)
across different modes and also with a pbs storage. For suspend mode relative
patterns are already working. To not break that behavior, and because pxar
and proxmox-backup-client also support relative patterns, allow them for the
other modes as well.
pve-guest-common:
Fabian Ebner (1):
vzdump: update exclude-path description
PVE/VZDump/Common.pm | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
pve-docs:
Fabian Ebner (1):
vdzump: extend examples to also cover relative patterns
vzdump.adoc | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
pve-container:
Fabian Ebner (3):
vzdump: turn findexcl into its own variable
vzdump: allow relative exclude patterns for snapshot and stop mode
vzdump: pass along exclude patterns to proxmox-backup-client
src/PVE/VZDump/LXC.pm | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
--
2.20.1
next reply other threads:[~2020-11-20 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 14:50 Fabian Ebner [this message]
2020-11-20 14:50 ` [pve-devel] [PATCH guest-common 1/5] vzdump: update exclude-path description Fabian Ebner
2020-11-20 14:50 ` [pve-devel] [PATCH docs 2/5] vdzump: extend examples to also cover relative patterns Fabian Ebner
2020-11-20 14:50 ` [pve-devel] [PATCH container 3/5] vzdump: turn findexcl into its own variable Fabian Ebner
2020-11-20 14:50 ` [pve-devel] [PATCH container 4/5] vzdump: allow relative exclude patterns for snapshot and stop mode Fabian Ebner
2020-11-20 14:50 ` [pve-devel] [PATCH container 5/5] vzdump: pass along exclude patterns to proxmox-backup-client Fabian Ebner
2020-11-24 16:03 ` [pve-devel] applied-series: [PATCH-SERIES] unify vzdump exclude-path behavior Fabian Grünbichler
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=20201120145045.31543-1-f.ebner@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