From: Christoph Heiss <c.heiss@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH docs 0/8] improve & unify installation(-related) documentation
Date: Mon, 4 Mar 2024 14:21:47 +0100 [thread overview]
Message-ID: <20240304132159.899727-1-c.heiss@proxmox.com> (raw)
This series in short tries to bring the documentation for the
ISO installation flow and anything related to it in line the with
respective documentation for PVE. As both products use the same
installer (minus small differences such as LVM options and BTRFS
support) and overall same basic system setup, it is worth to unify them.
This also brings the benefit that future changes should be more easily
adaptable to both.
As this essentially takes the "best of both worlds" in tries to combine
them, an accompanying series is also provided for `pve-docs` on the
respective mailing list - so please also take a look there.
FWIW; happy to further improve these sections if there suggestions,
since I'm already changing a lot anyway.
Christoph Heiss (8):
gitignore: add package build outputs
getting-help: align wording with respective pve-docs page
getting-help: add mailing lists link
installation: repos: improve & align wording with pve-docs
installation: iso: improve & align wording with pve-docs
installation: lvm-options: improve & align wording with pve-docs
installation: debian: improve & align wording with pve-docs
installation: zfs: add advanced zfs configuration section
.gitignore | 4 +
getting-help.adoc | 40 +++++---
pmg-installation.adoc | 232 ++++++++++++++++++++++++------------------
3 files changed, 165 insertions(+), 111 deletions(-)
--
2.43.0
next reply other threads:[~2024-03-04 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:21 Christoph Heiss [this message]
2024-03-04 13:21 ` [pmg-devel] [PATCH docs 1/8] gitignore: add package build outputs Christoph Heiss
2024-03-04 13:21 ` [pmg-devel] [PATCH docs 2/8] getting-help: align wording with respective pve-docs page Christoph Heiss
2024-03-04 13:21 ` [pmg-devel] [PATCH docs 3/8] getting-help: add mailing lists link Christoph Heiss
2024-03-04 13:21 ` [pmg-devel] [PATCH docs 4/8] installation: repos: improve & align wording with pve-docs Christoph Heiss
2024-03-04 13:21 ` [pmg-devel] [PATCH docs 5/8] installation: iso: " Christoph Heiss
2024-03-04 13:21 ` [pmg-devel] [PATCH docs 6/8] installation: lvm-options: " Christoph Heiss
2024-03-04 13:21 ` [pmg-devel] [PATCH docs 7/8] installation: debian: " Christoph Heiss
2024-03-04 13:21 ` [pmg-devel] [PATCH docs 8/8] installation: zfs: add advanced zfs configuration section Christoph Heiss
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=20240304132159.899727-1-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pmg-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