From: Alexander Zeidler <a.zeidler@proxmox.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>
Cc: pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [PATCH pmg-docs 2/2] installation: add section 'Firmware Updates' & repository
Date: Wed, 24 Jan 2024 16:04:16 +0100 [thread overview]
Message-ID: <31ec4ffcb71bd9241925579535548474df64a4a3.camel@proxmox.com> (raw)
In-Reply-To: <Za6rh9P1KQfV9Z_s@rosa.proxmox.com>
On Mon, 2024-01-22 at 18:53 +0100, Stoiko Ivanov wrote:
> Content-wise this looks very good - thanks!
>
> I just wondered if the 'Installation' chapter is the appropriate location
> for this - I'd rather look for it in the 'Administration' chapter.
>
> While the same could arguably be said about the p7zip-rar and libclamunrar
> installation above - this is just 1 paragraph as opposed to the quite
> detailed documentation in this patch
>
> Don't feel too strongly about this - so could go in as is as well - but
> adding it as separate 6.5 under Administration might have some merit
>
> What do you think?
Sounds good. Especially since it is partly a recurring manual task.
Thanks, here's v2:
https://lists.proxmox.com/pipermail/pmg-devel/2024-January/002658.html
next prev parent reply other threads:[~2024-01-24 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 13:54 [pmg-devel] [PATCH pmg-docs 1/2] installation: rephrase section "Other Repository Sources" Alexander Zeidler
2023-11-03 13:54 ` [pmg-devel] [PATCH pmg-docs 2/2] installation: add section 'Firmware Updates' & repository Alexander Zeidler
2024-01-22 17:53 ` Stoiko Ivanov
2024-01-24 15:04 ` Alexander Zeidler [this message]
2023-12-19 13:43 ` [pmg-devel] [PATCH pmg-docs 1/2] installation: rephrase section "Other Repository Sources" Alexander Zeidler
2024-01-22 17:49 ` [pmg-devel] applied: " Stoiko Ivanov
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=31ec4ffcb71bd9241925579535548474df64a4a3.camel@proxmox.com \
--to=a.zeidler@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=s.ivanov@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