From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 docs] pvesm: mark ZFS level as both
Date: Tue, 6 Jun 2023 18:02:05 +0200 [thread overview]
Message-ID: <53597a10-2e8a-b753-98bb-4786b55c8c5d@proxmox.com> (raw)
In-Reply-To: <20230411110442.362000-1-a.lauterer@proxmox.com>
Am 11/04/2023 um 13:04 schrieb Aaron Lauterer:
> ZFS can do both, and we do use both, block and file level functionality.
>
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
> changes since v1: rephrased the footnote for ZFS
>
> pvesm.adoc | 39 +++++++++++++++++++++------------------
> 1 file changed, 21 insertions(+), 18 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2023-06-06 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 11:04 [pve-devel] " Aaron Lauterer
2023-06-06 16:02 ` 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=53597a10-2e8a-b753-98bb-4786b55c8c5d@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@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