From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH docs 0/2] update proxmox-boot-tool docs
Date: Tue, 26 Apr 2022 12:56:02 +0200 [thread overview]
Message-ID: <399b81d4-e83c-7482-17e9-6321f81e3876@proxmox.com> (raw)
In-Reply-To: <20220412094614.2123910-1-s.ivanov@proxmox.com>
On 12.04.22 11:46, Stoiko Ivanov wrote:
> the 2 patches are independent of each other (I had overlooked 3479 for a while)
>
> Stoiko Ivanov (2):
> zfs: fix #3479 rephrase boot-loader description.
> sys: boot: minimally document kernel version pinning
>
> local-zfs.adoc | 8 ++++++--
> system-booting.adoc | 48 +++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 54 insertions(+), 2 deletions(-)
>
applied, thanks!
prev parent reply other threads:[~2022-04-26 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 9:46 [pve-devel] " Stoiko Ivanov
2022-04-12 9:46 ` [pve-devel] [PATCH docs 1/2] zfs: fix #3479 rephrase boot-loader description Stoiko Ivanov
2022-04-12 9:46 ` [pve-devel] [PATCH docs 2/2] sys: boot: minimally document kernel version pinning Stoiko Ivanov
2022-04-26 10:56 ` 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=399b81d4-e83c-7482-17e9-6321f81e3876@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-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