From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Mira Limbeck <m.limbeck@proxmox.com>,
pve-devel@pve.proxmox.com
Subject: [pve-devel] applied: [PATCH docs] add clarification of experimental zfs encryption status
Date: Tue, 12 Jul 2022 09:09:48 +0200 [thread overview]
Message-ID: <5d187b95-e731-c285-73c9-8f71b4aa4f56@proxmox.com> (raw)
In-Reply-To: <20220706143653.1712334-1-m.limbeck@proxmox.com>
Am 06/07/2022 um 16:36 schrieb Mira Limbeck:
> Signed-off-by: Mira Limbeck <m.limbeck@proxmox.com>
> ---
> local-zfs.adoc | 6 ++++++
> 1 file changed, 6 insertions(+)
>
>
applied, thanks! Amended the patch to drop the newly added trailing white space
after "ZVOLs. "
prev parent reply other threads:[~2022-07-12 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 14:36 [pve-devel] " Mira Limbeck
2022-07-12 7:09 ` 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=5d187b95-e731-c285-73c9-8f71b4aa4f56@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.limbeck@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=pve-devel@pve.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