From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES v5] fix #2649: introduce prune-backups property for storages supporting backups
Date: Tue, 29 Sep 2020 10:37:03 +0200 [thread overview]
Message-ID: <20200929083705.20124-1-f.ebner@proxmox.com> (raw)
Make use of the new 'prune-backups' storage property with vzdump.
Changes from v4:
* drop already applied patches
* rebase on current master
* fix typo
* add newline to error message
Fabian Ebner (2):
Allow prune-backups as an alternative to maxfiles
Always use prune-backups instead of maxfiles internally
PVE/API2/VZDump.pm | 4 +--
PVE/VZDump.pm | 72 +++++++++++++++++++++++++++++++---------------
2 files changed, 51 insertions(+), 25 deletions(-)
--
2.20.1
next reply other threads:[~2020-09-29 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 8:37 Fabian Ebner [this message]
2020-09-29 8:37 ` [pve-devel] [PATCH v5 manager 1/2] Allow prune-backups as an alternative to maxfiles Fabian Ebner
2020-09-29 8:37 ` [pve-devel] [PATCH v5 manager 2/2] Always use prune-backups instead of maxfiles internally Fabian Ebner
2020-10-01 14:36 ` [pve-devel] applied: [PATCH-SERIES v5] fix #2649: introduce prune-backups property for storages supporting backups 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=20200929083705.20124-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