From: "Léo Le Bouter via Guix-patches via" <guix-patches@gnu.org>
To: raid5atemyhomework <raid5atemyhomework@protonmail.com>,
46366@debbugs.gnu.org
Subject: [bug#46366] [PATCH] gnu: Update zfs.
Date: Sun, 07 Feb 2021 18:06:57 +0100 [thread overview]
Message-ID: <23ee06981b4ffb80b60552660e10f1fac033bdcf.camel@zaclys.net> (raw)
In-Reply-To: <_hvdoCw7bHSZrJPgytlhM_ghWCUY2yS3YFTK4yxMPNWxzdYCayYtYeKuOyvlKIGpt2BRvr5kBsHIo9HPmLjX3GR4vhc5ifpOkkmzIFcuhh0=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Sun, 2021-02-07 at 15:18 +0000, raid5atemyhomework via Guix-patches
via wrote:
> I am fairly unmotivated to continue working on ZFS-on-Guix, but
> anyway.
> 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 am interested by ZFS on GNU Guix but I am not sure I understand
Scheme enough to review your patches. Also, it makes it a bit confusing
that your patches are submitted as several separate bugs. I think it
would make it easier to review if they were all summed into a single
"ZFS on GNU Guix System" bug. Otherwise I think it will take a bit of
patience, I'm sure you've seen the amount of pending patches, we're
near a thousand by now. Lots of things to review, limited time.
All in all, just remember that I am very enthusiastic about ZFS on GNU
Guix! I'm sure lots of people are.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-07 17:09 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 [this message]
2021-02-08 0:23 ` [bug#46366] Sharlatan Hellseher
2021-02-08 2:51 ` [bug#46366] [PATCH] gnu: Update zfs Danny Milosavljevic
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23ee06981b4ffb80b60552660e10f1fac033bdcf.camel@zaclys.net \
--to=guix-patches@gnu.org \
--cc=46366@debbugs.gnu.org \
--cc=lle-bout@zaclys.net \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).