From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexander Zeidler <a.zeidler@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs 1/2] secure boot: fix typos, add inline code formatting
Date: Tue, 28 Nov 2023 16:18:17 +0100 [thread overview]
Message-ID: <100cdf71-9529-4fee-9091-b0addc56a90b@proxmox.com> (raw)
In-Reply-To: <20231128135629.123748-1-a.zeidler@proxmox.com>
Am 28/11/2023 um 14:56 schrieb Alexander Zeidler:
> Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
> ---
> system-booting.adoc | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
>
applied series, thanks!
prev parent reply other threads:[~2023-11-28 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 13:56 [pve-devel] " Alexander Zeidler
2023-11-28 13:56 ` [pve-devel] [PATCH docs 2/2] installation: be more specific about current secure boot state Alexander Zeidler
2023-11-28 15:18 ` 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=100cdf71-9529-4fee-9091-b0addc56a90b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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