From: Robert Obkircher <r.obkircher@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH v1 proxmox-backup] www: regenerate OnlineHelpInfo.js
Date: Tue, 2 Jun 2026 15:28:33 +0200 [thread overview]
Message-ID: <20260602132838.234127-1-r.obkircher@proxmox.com> (raw)
Those new labels seem to be unused, but it is a bit inconvenient that
commands like "make -C www" modify tracked files.
Fixes: 304f6d19251f ("docs: describe s3 request notifications and threshold reset schedule")
Signed-off-by: Robert Obkircher <r.obkircher@proxmox.com>
---
www/OnlineHelpInfo.js | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/www/OnlineHelpInfo.js b/www/OnlineHelpInfo.js
index e118b0add..6f809f007 100644
--- a/www/OnlineHelpInfo.js
+++ b/www/OnlineHelpInfo.js
@@ -271,6 +271,10 @@ const proxmoxOnlineHelpInfo = {
"link": "/docs/notifications.html#notification-mode",
"title": "Notification Mode"
},
+ "s3-notification-thresholds": {
+ "link": "/docs/notifications.html#s3-notification-thresholds",
+ "title": "Notification Thresholds and Reset Schedule (S3 Datastores Only)"
+ },
"pve-integration": {
"link": "/docs/pve-integration.html#pve-integration",
"title": "`Proxmox VE`_ Integration"
@@ -303,6 +307,10 @@ const proxmoxOnlineHelpInfo = {
"link": "/docs/storage.html#storage-move-namespaces-groups",
"title": "Moving Namespaces and Groups"
},
+ "datastore-options": {
+ "link": "/docs/storage.html#datastore-options",
+ "title": "Options"
+ },
"datastore-tuning-options": {
"link": "/docs/storage.html#datastore-tuning-options",
"title": "Tuning"
--
2.47.3
next reply other threads:[~2026-06-02 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 13:28 Robert Obkircher [this message]
2026-06-03 8:58 ` [PATCH v1 proxmox-backup] www: regenerate OnlineHelpInfo.js Christian Ebner
2026-06-03 10:33 ` applied: " Fabian Grünbichler
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=20260602132838.234127-1-r.obkircher@proxmox.com \
--to=r.obkircher@proxmox.com \
--cc=pbs-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.