From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christian Ebner <c.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-manager] www: backup: clarify experimental change detection modes
Date: Tue, 30 Jul 2024 19:55:58 +0200 [thread overview]
Message-ID: <4c381409-9625-459f-844f-ebd6d79357f5@proxmox.com> (raw)
In-Reply-To: <20240626070013.34880-1-c.ebner@proxmox.com>
Am 26/06/2024 um 09:00 schrieb Christian Ebner:
> Currently, the whole mode selector is labeled as experimental, this
> does however give the impression that also the default legacy mode is
> an experimental mode.
> To clarify that only the `data` and `metadata` change detection modes
> are experimental, move the experimental label to the individual
> modes and explicitly mention the experimental modes in the message.
>
> Also, make it more clear that the archive encoding format depends on
> the selected mode.
>
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
> www/manager6/panel/BackupAdvancedOptions.js | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
>
Just for the record: This was already applied by Fabian [0], thanks!
[0]: https://git.proxmox.com/?p=pve-manager.git;a=commit;h=8504a0e29132e01101a28f9dafcc930fd6cab95d
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-07-30 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 7:00 [pve-devel] " Christian Ebner
2024-07-30 17:55 ` 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=4c381409-9625-459f-844f-ebd6d79357f5@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.