From: Christian Ebner <c.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager] ui: remove experimental from change detection modes description
Date: Mon, 11 Nov 2024 12:55:14 +0100 [thread overview]
Message-ID: <20241111115515.233382-1-c.ebner@proxmox.com> (raw)
As no issues with the change detection mode set to `metadata` or
`data` have been reported during the prolonged test period, drop the
`experimental` warnings from the description.
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
www/manager6/panel/BackupAdvancedOptions.js | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/www/manager6/panel/BackupAdvancedOptions.js b/www/manager6/panel/BackupAdvancedOptions.js
index baa35e7f..a7b0fc2b 100644
--- a/www/manager6/panel/BackupAdvancedOptions.js
+++ b/www/manager6/panel/BackupAdvancedOptions.js
@@ -272,14 +272,14 @@ Ext.define('PVE.panel.BackupAdvancedOptions', {
value: '__default__',
comboItems: [
['__default__', "Default"],
- ['data', "Data (experimental)"],
- ['metadata', "Metadata (experimental)"],
+ ['data', "Data"],
+ ['metadata', "Metadata"],
],
},
endFlex: 2,
endColumn: {
xtype: 'displayfield',
- value: gettext("Mode to detect file changes and switch archive encoding format for container backups (NOTE: `data` and `metadata` modes are experimental)."),
+ value: gettext("Mode to detect file changes and switch archive encoding format for container backups."),
},
},
{
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-11-11 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 11:55 Christian Ebner [this message]
2024-11-11 11:55 ` [pve-devel] [PATCH docs] docs: drop experimental warning for change detection modes Christian Ebner
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=20241111115515.233382-1-c.ebner@proxmox.com \
--to=c.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