From: Manuel Federanko <m.federanko@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [pdm-devel] [PATCH datacenter-manager 0/3] docs: fix formatting of local-zfs docs
Date: Thu, 22 Jan 2026 12:21:02 +0100 [thread overview]
Message-ID: <20260122112106.118611-1-m.federanko@proxmox.com> (raw)
Fixed headings and code blocks, fixed grammar of one sentence.
The 3rd patch switches commands, file paths and config options/values to
be inline code blocks instead of cursive - I wasn't sure if that was
intentional, but this feels better and is easier to read imo, feedback
is appreciated.
Manuel Federanko (3):
docs: fix formatting of local-zfs documentation.
docs: remove superfluous "setup" in zfs documentation.
docs: make commands, file paths and config options inline code blocks.
docs/local-zfs.rst | 99 ++++++++++++++++++++++++----------------------
1 file changed, 52 insertions(+), 47 deletions(-)
--
2.47.3
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next reply other threads:[~2026-01-22 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 11:21 Manuel Federanko [this message]
2026-01-22 11:21 ` [pdm-devel] [PATCH datacenter-manager 1/3] docs: fix formatting of local-zfs documentation Manuel Federanko
2026-01-22 11:21 ` [pdm-devel] [PATCH datacenter-manager 2/3] docs: remove superfluous "setup" in zfs documentation Manuel Federanko
2026-01-22 11:21 ` [pdm-devel] [PATCH datacenter-manager 3/3] docs: make commands, file paths and config options inline code blocks Manuel Federanko
2026-01-22 12:53 ` Manuel Federanko
2026-01-23 10:21 ` Lukas Wagner
2026-01-23 10:15 ` [pdm-devel] applied: [PATCH datacenter-manager 0/3] docs: fix formatting of local-zfs docs Lukas Wagner
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=20260122112106.118611-1-m.federanko@proxmox.com \
--to=m.federanko@proxmox.com \
--cc=pdm-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.