From: raid5atemyhomework <raid5atemyhomework@protonmail.com>
To: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [bug#50347] [RFC PATCH] lint: Warn about kernel modules with a suspect license
Date: Sat, 04 Sep 2021 18:04:01 +0000 [thread overview]
Message-ID: <uBb-beWSE-IRQID75fF9NLDKxd5m3NvtW3119HWD_Wtd7DqzJZR0rdnRYdJSuNU5o8-gj9p7wXlsaz9CFAGKWBDPjKjnZ2xyCffa8pOucpw=@protonmail.com> (raw)
Hi list,
I hope this topic gets attention. As far as I can tell, this is a blocker against 45692 getting merged.
I am already annoyed enough with 45692 (it has been about half a year or so since submitted) and will not prioritize updating the patch until I can expect the CDDL-GPL incompatibility issue to be resolved somehow. Thank you to Maxime Devos for at least reviewing the final key patch to *start* ZFS support.
I know a few people have asked me for help in getting ZFS working on *their* Guix systmes; I really hope they can speak up on public forums so that others know that ZFS support on Guix is desired by more than just me. Honestly, the only reason I use Guix is because this is the only FSF-recommended distribution with a recent ZFS available (I know how to code in Scheme, but only in anger; I prefer C++ or Haskell); but if Guix removes ZFS, I would rather install a non-FSF-recommended distribution than lose more of my homework to lousy RAID5 implementations.
Thanks
raid5atemyhomework
next reply other threads:[~2021-09-04 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 18:04 raid5atemyhomework [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-02 21:42 [bug#50347] [RFC PATCH] lint: Warn about kernel modules with a suspect license Maxime Devos
2021-09-02 22:20 ` Maxime Devos
2021-09-06 8:23 ` zimoun
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='uBb-beWSE-IRQID75fF9NLDKxd5m3NvtW3119HWD_Wtd7DqzJZR0rdnRYdJSuNU5o8-gj9p7wXlsaz9CFAGKWBDPjKjnZ2xyCffa8pOucpw=@protonmail.com' \
--to=raid5atemyhomework@protonmail.com \
--cc=guix-devel@gnu.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.
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).