From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fabian Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH-SERIES v5] fix #2649: introduce prune-backups property for storages supporting backups
Date: Thu, 1 Oct 2020 16:36:46 +0200 [thread overview]
Message-ID: <c7d59e10-e68a-6230-44b2-38aeeb46e841@proxmox.com> (raw)
In-Reply-To: <20200929083705.20124-1-f.ebner@proxmox.com>
On 29.09.20 10:37, Fabian Ebner wrote:
> 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(-)
>
for the record: I have to admit that I did no big testing rounds with this, but the
previous was, besides of the faulty fallback, OK IIRC and the fallback stuff was fixed,
so...
applied, thanks!
prev parent reply other threads:[~2020-10-01 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 8:37 [pve-devel] " Fabian Ebner
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 ` 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=c7d59e10-e68a-6230-44b2-38aeeb46e841@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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