From: "Dominic Jäger" <d.jaeger@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] installation: Fix & move link
Date: Mon, 3 Aug 2020 13:07:35 +0200 [thread overview]
Message-ID: <20200803110735.874501-1-d.jaeger@proxmox.com> (raw)
Dashes --- put the "Install PVE on Debian Buster" link into a code segment on
pve.proxmox.com/wiki/Installation.
Additionally, the both links are not ZFS performance tips => Move them further
below.
Signed-off-by: Dominic Jäger <d.jaeger@proxmox.com>
---
This is still untested because I am struggling a little to run our wiki
locally. So if someone thinks this might work, please apply, or if you have a
better idea, just ignore the patch. Otherwise I'll try to run the wiki locally
again tomorrow.
pve-installation.adoc | 14 ++++----------
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/pve-installation.adoc b/pve-installation.adoc
index 0d416ac..6a59b2c 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -270,16 +270,6 @@ following command:
# zpool add <pool-name> log </dev/path_to_fast_ssd>
----
-ifdef::wiki[]
-
-link:/wiki/Prepare_Installation_Media[Prepare Installation Media]
----------------------------------------------------------
-
-link:/wiki/Install_Proxmox_VE_on_Debian_Buster[Install Proxmox VE on Debian Buster]
------------------------------------------------------------------------------------
-
-endif::wiki[]
-
ifndef::wiki[]
Install {pve} on Debian
@@ -324,6 +314,10 @@ Video Tutorials
See Also
--------
+* link:/wiki/Prepare_Installation_Media[Prepare Installation Media]
+
+* link:/wiki/Install_Proxmox_VE_on_Debian_Buster[Install Proxmox VE on Debian Buster]
+
* link:/wiki/System_Requirements[System Requirements]
* link:/wiki/Package_Repositories[Package Repositories]
--
2.20.1
next reply other threads:[~2020-08-03 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 11:07 Dominic Jäger [this message]
2020-08-20 13:30 ` [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=20200803110735.874501-1-d.jaeger@proxmox.com \
--to=d.jaeger@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.