From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 guest-common 1/3] mention prune behavior for the remove parameter
Date: Wed, 3 Mar 2021 12:50:40 +0100 [thread overview]
Message-ID: <20210303115042.22061-1-f.ebner@proxmox.com> (raw)
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
---
First version here (it's been a while):
https://lists.proxmox.com/pipermail/pve-devel/2020-October/045585.html
Changes from v1:
* Space lines more evenly to get below 80 char limit.
PVE/VZDump/Common.pm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/PVE/VZDump/Common.pm b/PVE/VZDump/Common.pm
index 86cb7bd..bc38343 100644
--- a/PVE/VZDump/Common.pm
+++ b/PVE/VZDump/Common.pm
@@ -231,7 +231,8 @@ my $confdesc = {
}),
remove => {
type => 'boolean',
- description => "Remove old backup files if there are more than 'maxfiles' backup files.",
+ description => "Remove old backup files if there are more than " .
+ "'maxfiles' backup files or prune according to 'prune-backups'.",
optional => 1,
default => 1,
},
--
2.20.1
next reply other threads:[~2021-03-03 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 11:50 Fabian Ebner [this message]
2021-03-03 11:50 ` [pve-devel] [PATCH v2 manager 2/3] partially fix #2745: vzdump: use default for " Fabian Ebner
2021-03-05 20:34 ` [pve-devel] applied: " Thomas Lamprecht
2021-03-03 11:50 ` [pve-devel] [PATCH v2 manager 3/3] fix #2745: ui: backup: allow users to specify remove=1 Fabian Ebner
2021-03-05 20:34 ` Thomas Lamprecht
2021-03-09 10:28 ` Fabian Ebner
2021-03-09 10:53 ` Fabian Ebner
2021-03-05 20:34 ` [pve-devel] applied: [PATCH v2 guest-common 1/3] mention prune behavior for the remove parameter 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=20210303115042.22061-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