From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager v2 1/4] ui: qemu: AudioEdit: enable online help link
Date: Mon, 7 Jul 2025 11:14:07 +0200 [thread overview]
Message-ID: <20250707091412.314631-2-c.heiss@proxmox.com> (raw)
In-Reply-To: <20250707091412.314631-1-c.heiss@proxmox.com>
This section has been available since pve-docs 6.0-5, which was released
in October 2019.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
Changes v1 -> v2:
* rebased on latest master
www/manager6/qemu/AudioEdit.js | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/www/manager6/qemu/AudioEdit.js b/www/manager6/qemu/AudioEdit.js
index 64c518373..ba588edcd 100644
--- a/www/manager6/qemu/AudioEdit.js
+++ b/www/manager6/qemu/AudioEdit.js
@@ -2,8 +2,7 @@ Ext.define('PVE.qemu.AudioInputPanel', {
extend: 'Proxmox.panel.InputPanel',
xtype: 'pveAudioInputPanel',
- // FIXME: enable once we bumped doc-gen so this ref is included
- //onlineHelp: 'qm_audio_device',
+ onlineHelp: 'qm_audio_device',
onGetValues: function (values) {
var ret = PVE.Parser.printPropertyString(values);
--
2.49.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-07 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 9:14 [pve-devel] [PATCH manager v2 0/4] improve some onlineHelp links Christoph Heiss
2025-07-07 9:14 ` Christoph Heiss [this message]
2025-07-07 9:14 ` [pve-devel] [PATCH manager v2 2/4] ui: qemu: HDTPM: enable online help link Christoph Heiss
2025-07-07 9:14 ` [pve-devel] [PATCH manager v2 3/4] ui: panel: TagConfig: link to more specific online help section Christoph Heiss
2025-07-07 9:14 ` [pve-devel] [PATCH manager v2 4/4] ui: dc: tag edit: use more specific documentation section Christoph Heiss
2025-07-08 10:27 ` [pve-devel] applied-series: [PATCH manager v2 0/4] improve some onlineHelp links 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=20250707091412.314631-2-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox