From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christoph Heiss <c.heiss@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH docs v3 0/5] improve & unify installation(-related) documentation
Date: Fri, 22 Mar 2024 11:34:06 +0100 [thread overview]
Message-ID: <d417e9ca-a18c-4616-a8ed-066a1b55820e@proxmox.com> (raw)
In-Reply-To: <20240321152941.1971509-1-c.heiss@proxmox.com>
On 21/03/2024 16:29, Christoph Heiss wrote:
> 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 PMG. 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 unifying them.
>
> There is (of course) still room for improvement, esp. regarding the apt
> repo/update section as pointed out by Alex. Still like to get this in
> rather sooner than later, to not diverge even more.
>
> I'll send the appropriate pmg-docs series (see v1 of that [0]) when this
> has been finalized & applied, to keep it transparent and easier to
> reason about.
>
> [0] https://lists.proxmox.com/pipermail/pmg-devel/2024-March/002870.html
>
> Revision history
> ----------------
> v1: https://lists.proxmox.com/pipermail/pve-devel/2024-March/062056.html
> v2: https://lists.proxmox.com/pipermail/pve-devel/2024-March/062159.html
>
> Notable changes v1 -> v2:
> * dropped already-applied patches
> * slight rewording in some places based on suggestions
>
> Notable changes v2 -> v3:
> * fixed small typo
>
> Christoph Heiss (5):
> package-repos: improve wording partly based on pmg-docs
> installation: iso: improve & align wording with pmg-docs
> installation: lvm-options: improve & align wording with pmg-docs
> installation: zfs-options: improve & align wording with pmg-docs
> installation: iso: reflow location and password dialog screenshots
>
> pve-installation.adoc | 144 ++++++++++++++++++++++++++---------------
> pve-package-repos.adoc | 26 ++++----
> 2 files changed, 107 insertions(+), 63 deletions(-)
>
applied series, thanks!
prev parent reply other threads:[~2024-03-22 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 15:29 [pve-devel] " Christoph Heiss
2024-03-21 15:29 ` [pve-devel] [PATCH docs v3 1/5] package-repos: improve wording partly based on pmg-docs Christoph Heiss
2024-03-21 15:29 ` [pve-devel] [PATCH docs v3 2/5] installation: iso: improve & align wording with pmg-docs Christoph Heiss
2024-03-21 15:29 ` [pve-devel] [PATCH docs v3 3/5] installation: lvm-options: " Christoph Heiss
2024-03-21 15:29 ` [pve-devel] [PATCH docs v3 4/5] installation: zfs-options: " Christoph Heiss
2024-03-21 15:29 ` [pve-devel] [PATCH docs v3 5/5] installation: iso: reflow location and password dialog screenshots Christoph Heiss
2024-03-22 10:34 ` Thomas Lamprecht [this message]
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=d417e9ca-a18c-4616-a8ed-066a1b55820e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@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