From: Danny Milosavljevic <dannym@scratchpost.org>
To: 46366@debbugs.gnu.org
Cc: raid5atemyhomework <raid5atemyhomework@protonmail.com>,
46366-done@debbugs.gnu.org
Subject: [bug#46366] [PATCH] gnu: Update zfs.
Date: Mon, 8 Feb 2021 03:51:56 +0100 [thread overview]
Message-ID: <20210208035156.5ebd959a@scratchpost.org> (raw)
In-Reply-To: <_hvdoCw7bHSZrJPgytlhM_ghWCUY2yS3YFTK4yxMPNWxzdYCayYtYeKuOyvlKIGpt2BRvr5kBsHIo9HPmLjX3GR4vhc5ifpOkkmzIFcuhh0=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Hi raid5atemyhomework,
On Sun, 07 Feb 2021 15:18:34 +0000
raid5atemyhomework via Guix-patches via <guix-patches@gnu.org> wrote:
> I am fairly unmotivated to continue working on ZFS-on-Guix, but anyway. Here's an update of ZFS to 2.0.2, at least.
>
> Tested only with `./pre-inst-env guix build zfs` on a patched Guix. Fairly unmotivated to do more testing since there is no real interest in getting my patches merged. Posting here just in case somebody actually gets interested.
>
> I have ZFS and Guix on a fileserver I'm using in a homelab for my homework. It's working for now. Not really interested in pushing for better ZFS support anymore since I'm tired and need to get on with my homework.
I totally understand.
It's frustrating when well-tested complete patches get unanswered for several
weeks--it happened to me before.
In any case, I've asked whether someone who knows how to create a profile
in a service can finally review your patches.
I'm sorry.
Pushed the update of the zfs package to 2.0.2 to guix master as
commit 5424ca6d6e01672bf7304a4144b05a98852adbab.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-02-08 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 15:18 [bug#46366] [PATCH] gnu: Update zfs raid5atemyhomework via Guix-patches via
2021-02-07 17:06 ` Léo Le Bouter via Guix-patches via
2021-02-08 0:23 ` [bug#46366] Sharlatan Hellseher
2021-02-08 2:51 ` Danny Milosavljevic [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=20210208035156.5ebd959a@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=46366-done@debbugs.gnu.org \
--cc=46366@debbugs.gnu.org \
--cc=raid5atemyhomework@protonmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.