From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 0/4] improve some onlineHelp links
Date: Wed, 28 May 2025 11:29:20 +0200 [thread overview]
Message-ID: <20250528092927.253490-1-c.heiss@proxmox.com> (raw)
Came across these commented-out `onlineHelp` and looked into it - all
referenced sections across the repo have been (very) long available in
pve-docs and can thus be enabled.
Additionally, after looking at #3, thought to link to this "new" section
in some other tags-related panels, instead of the datacenter
configuration file.
Christoph Heiss (4):
ui: qemu: AudioEdit: enable online help link
ui: qemu: HDTPM: enable online help link
ui: panel: TagConfig: link to more specific online help section
ui: dc: tag edit: use more specific documentation section
debian/control | 2 +-
www/manager6/dc/OptionView.js | 2 +-
www/manager6/dc/RegisteredTagsEdit.js | 2 +-
www/manager6/dc/UserTagAccessEdit.js | 2 +-
www/manager6/panel/TagConfig.js | 3 +--
www/manager6/qemu/AudioEdit.js | 3 +--
www/manager6/qemu/HDTPM.js | 2 +-
7 files changed, 7 insertions(+), 9 deletions(-)
--
2.49.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-05-28 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 9:29 Christoph Heiss [this message]
2025-05-28 9:29 ` [pve-devel] [PATCH manager 1/4] ui: qemu: AudioEdit: enable online help link Christoph Heiss
2025-05-28 9:29 ` [pve-devel] [PATCH manager 2/4] ui: qemu: HDTPM: " Christoph Heiss
2025-05-28 9:29 ` [pve-devel] [PATCH manager 3/4] ui: panel: TagConfig: link to more specific online help section Christoph Heiss
2025-05-28 9:29 ` [pve-devel] [PATCH manager 4/4] ui: dc: tag edit: use more specific documentation section Christoph Heiss
2025-07-07 9:16 ` [pve-devel] [PATCH manager 0/4] improve some onlineHelp links Christoph Heiss
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=20250528092927.253490-1-c.heiss@proxmox.com \
--to=c.heiss@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.