From: Dominik Rusovac <d.rusovac@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Dominik Rusovac <d.rusovac@proxmox.com>
Subject: [pve-devel] [PATCH docs v2] fix #7106: intro: replace broken link
Date: Fri, 5 Dec 2025 11:50:37 +0100 [thread overview]
Message-ID: <20251205105037.126730-1-d.rusovac@proxmox.com> (raw)
Broken link in section 1.11. now properly links to noVNC page.
Signed-off-by: Dominik Rusovac <d.rusovac@proxmox.com>
---
Notes:
Changes since v1:
- fix commit author
- make commit message more specific
v1: https://lore.proxmox.com/pve-devel/95d693b5-72d8-431a-9d37-803454f4f567@proxmox.com/T/#t
pve-intro.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pve-intro.adoc b/pve-intro.adoc
index 82f1495..2e16aca 100644
--- a/pve-intro.adoc
+++ b/pve-intro.adoc
@@ -232,7 +232,7 @@ infrastructure, and made it easy to provide additional services.
Also, the new REST API made it possible to replace the original user interface
with a modern client side single-page application using JavaScript. We also
replaced the old Java based VNC console code with
-https://kanaka.github.io/noVNC/[noVNC]. So you only need a web browser to manage
+https://novnc.com/info.html[noVNC]. So you only need a web browser to manage
your VMs.
The support for various storage types is another big task. Notably, {pve} was
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-12-05 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 10:50 Dominik Rusovac [this message]
2025-12-05 11:39 ` [pve-devel] applied: " 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=20251205105037.126730-1-d.rusovac@proxmox.com \
--to=d.rusovac@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