From: Moayad Almalat <m.almalat@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Graeme Seaton <lists@graemes.com>
Subject: Re: [pve-devel] OpenZFS 2.0
Date: Wed, 2 Dec 2020 14:10:01 +0100 (CET) [thread overview]
Message-ID: <37072031.541.1606914601508@webmail.proxmox.com> (raw)
In-Reply-To: <019e33dd-6722-f2b2-24a3-f41d59f1527b@graemes.com>
This thread will inform you :)
https://forum.proxmox.com/threads/openzfs-2-0.79948/
> On 12/02/2020 1:45 PM Graeme Seaton <lists@graemes.com> wrote:
>
>
> Hi,
>
> Notice that OpenZFS 2.0 has been officially released at:
> https://github.com/openzfs/zfs/releases/tag/zfs-2.0.0
>
> Is integration into PVE on the roadmap? (I'm a sucker for new toys ;-) )
>
> Regards,
>
> Graeme
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
best regards,
Moayad Almalat
next prev parent reply other threads:[~2020-12-02 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 12:45 Graeme Seaton
2020-12-02 13:10 ` Moayad Almalat [this message]
2020-12-02 13:10 ` Thomas Lamprecht
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=37072031.541.1606914601508@webmail.proxmox.com \
--to=m.almalat@proxmox.com \
--cc=lists@graemes.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