From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zfs: update to 2.0.0
Date: Tue, 01 Dec 2020 03:46:27 +0100 [thread overview]
Message-ID: <20201201024627.6EkPyLfbzraZg83dH3m_Wy7BcfQ33bSBjw0y_mE9if8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26848@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/26848#issuecomment-736181037
Comment:
@Vaelatern I believe this is now ready to go, thanks to @ericonr for helping me figure out the necessary cflags to get `pam_zfscrypt` to compile. Along with @zdykstra and @ericonr, I have been using the releaes candidates for awhile (including in [zbm-dev/zfsbootmenu](https://github.com/zbm-dev/zfsbootmenu)) and have suffered no ill effects, even after upgrading my pools.
next prev parent reply other threads:[~2020-12-01 2:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 23:33 [PR PATCH] zfs: update to 2.0.0 [WIP] ahesford
2020-12-01 2:40 ` [PR PATCH] [Updated] " ahesford
2020-12-01 2:46 ` ahesford [this message]
2020-12-01 4:44 ` zfs: update to 2.0.0 zdykstra
2020-12-01 21:16 ` Vaelatern
2020-12-02 4:25 ` [PR PATCH] [Merged]: " Vaelatern
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=20201201024627.6EkPyLfbzraZg83dH3m_Wy7BcfQ33bSBjw0y_mE9if8@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).