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] fix: readme: replace broken link to AsciiDoc site
Date: Fri, 5 Dec 2025 13:42:40 +0100 [thread overview]
Message-ID: <20251205124240.170664-1-d.rusovac@proxmox.com> (raw)
Broken link in README now properly links to AsciiDoc site.
Signed-off-by: Dominik Rusovac <d.rusovac@proxmox.com>
---
README.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.adoc b/README.adoc
index 3d614e5..2289983 100644
--- a/README.adoc
+++ b/README.adoc
@@ -3,7 +3,7 @@ Proxmox VE Documentation
We try to generate high quality documentation for
{website}[{pve}], and choose to use
-http://www.methods.co.nz/asciidoc/[AsciiDoc] as base format.
+https://asciidoc.org/[AsciiDoc] as base format.
The basic idea is to generate high quality manual pages, and assemble
them into a complete book, called link:pve-admin-guide.adoc[Proxmox VE
--
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 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 12:42 Dominik Rusovac [this message]
2025-12-05 15:50 ` 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=20251205124240.170664-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