From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Dominik Rusovac <d.rusovac@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs v2] fix #7106: intro: replace broken link
Date: Fri, 5 Dec 2025 12:39:02 +0100 [thread overview]
Message-ID: <176493473863.4193559.4992788902843465339.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251205105037.126730-1-d.rusovac@proxmox.com>
On Fri, 05 Dec 2025 11:50:37 +0100, Dominik Rusovac wrote:
> Broken link in section 1.11. now properly links to noVNC page.
>
>
Applied, thanks!
I amended the commit message to also include "to noVNC site" as that makes it
more telling when browsing the git (oneline) log, and we often use the commit
message as base for writing the debian/changelog entries, so it makes the
maintainers life slightly easier if subject includes such info; no worries at
all though, just mentioning it.
[1/1] fix #7106: intro: replace broken link
commit: 6e135b14d9293738c0005800b4bc0e321fa4542f
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-12-05 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 10:50 [pve-devel] " Dominik Rusovac
2025-12-05 11:39 ` 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=176493473863.4193559.4992788902843465339.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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