From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zfs: divide under subpackages
Date: Tue, 28 Feb 2023 17:43:48 +0100 [thread overview]
Message-ID: <20230228164348.Td6eQfFiEHJXTEF79uRS0q5SaKNh5bg39iE9iBbqvu8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42484@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
New comment by Vaelatern on void-packages repository
https://github.com/void-linux/void-packages/pull/42484#issuecomment-1448504761
Comment:
Thank you for your contribution! Unfortunately, there are some red flags here that can not be cleaned up. ZFS lives in that special place in our systems where, if it dies, we end up with massive cleanup efforts (and probably restoration from backups). As such, anything that threatens stability, even so innocuous as separating userspace commands and kernel modules installed (which is arguably tested... in one direction), risks data.
I'm afraid we won't be able to merge this into Void.
next prev parent reply other threads:[~2023-02-28 16:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 14:38 [PR PATCH] " robertek
2023-02-28 13:04 ` [PR REVIEW] " ahesford
2023-02-28 13:04 ` ahesford
2023-02-28 13:04 ` ahesford
2023-02-28 13:48 ` robertek
2023-02-28 13:49 ` ahesford
2023-02-28 13:50 ` robertek
2023-02-28 13:52 ` robertek
2023-02-28 13:53 ` ahesford
2023-02-28 14:05 ` robertek
2023-02-28 14:28 ` ahesford
2023-02-28 16:43 ` [PR PATCH] [Closed]: " Vaelatern
2023-02-28 16:43 ` Vaelatern [this message]
2023-02-28 16:44 ` robertek
2023-02-28 16:45 ` robertek
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=20230228164348.Td6eQfFiEHJXTEF79uRS0q5SaKNh5bg39iE9iBbqvu8@z \
--to=vaelatern@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).