From: Alexander Zeidler <a.zeidler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs] sysadmin: add section 'Firmware Updates' and references
Date: Wed, 26 Jul 2023 14:02:53 +0200 [thread overview]
Message-ID: <a4817af37bdffa03fa34c91fd72bf5b402b1b30f.camel@proxmox.com> (raw)
In-Reply-To: <f06a9731-ad46-8d6c-3a91-cd929917a86d@proxmox.com>
On Wed, 2023-07-26 at 12:58 +0200, Aaron Lauterer wrote:
> Maybe something like this?
Great! Will also fix my overlooked line lengths.
prev parent reply other threads:[~2023-07-26 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 10:26 Alexander Zeidler
2023-07-26 10:58 ` Aaron Lauterer
2023-07-26 12:02 ` Alexander Zeidler [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=a4817af37bdffa03fa34c91fd72bf5b402b1b30f.camel@proxmox.com \
--to=a.zeidler@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