From: Alwin Antreich <a.antreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/2] move footnote of Ceph's intro into TIP section
Date: Fri, 25 Sep 2020 14:51:45 +0200 [thread overview]
Message-ID: <20200925125146.1945521-1-a.antreich@proxmox.com> (raw)
Signed-off-by: Alwin Antreich <a.antreich@proxmox.com>
---
Note: The footnote in the title section broke the link building for that
footnote when used with a variable on the beginning of the url.
The parser seems to look for an http(s) and considers it text
otherwise. But interestingly it worked with the other footnotes.
Should my note rather go into the commit message?
pveceph.adoc | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/pveceph.adoc b/pveceph.adoc
index baf0988..0f94b97 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -58,12 +58,14 @@ and VMs on the same node is possible.
To simplify management, we provide 'pveceph' - a tool to install and
manage {ceph} services on {pve} nodes.
-.Ceph consists of a couple of Daemons footnote:[Ceph intro https://docs.ceph.com/docs/{ceph_codename}/start/intro/], for use as a RBD storage:
+.Ceph consists of a couple of Daemons, for use as a RBD storage:
- Ceph Monitor (ceph-mon)
- Ceph Manager (ceph-mgr)
- Ceph OSD (ceph-osd; Object Storage Daemon)
-TIP: We highly recommend to get familiar with Ceph's architecture
+TIP: We highly recommend to get familiar with Ceph
+footnote:[Ceph intro https://docs.ceph.com/docs/{ceph_codename}/start/intro/],
+its architecture
footnote:[Ceph architecture https://docs.ceph.com/docs/{ceph_codename}/architecture/]
and vocabulary
footnote:[Ceph glossary https://docs.ceph.com/docs/{ceph_codename}/glossary].
--
2.27.0
next reply other threads:[~2020-09-25 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 12:51 Alwin Antreich [this message]
2020-09-25 12:51 ` [pve-devel] [PATCH docs 2/2] update links to the ceph docs Alwin Antreich
2020-10-12 12:42 ` [pve-devel] [PATCH docs 1/2] move footnote of Ceph's intro into TIP section Alwin Antreich
2020-10-14 10:28 ` [pve-devel] applied-series: " 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=20200925125146.1945521-1-a.antreich@proxmox.com \
--to=a.antreich@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