From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zfs: patch for linux-6.3
Date: Thu, 25 May 2023 04:43:57 +0200 [thread overview]
Message-ID: <20230525024357.g97IM2uddewC3DL3IIESx2COS4IBAE764OfzzCzgAx0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44073@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
New comment by Vaelatern on void-packages repository
https://github.com/void-linux/void-packages/pull/44073#issuecomment-1562174730
Comment:
These are pretty heavy patches to keep in our tree, and yet how do we know these are all the relevant patches? I'm more comfortable waiting for newer ZFS.
To be clear I'm sure these are all the 5 patches in linux-specific compat. I'm less sure the patches can be considered safe without the other patches in the upcoming release, and they are too heavy for me to reasonably audit, as well as being quite heavy for the eternal history of the void-packages repo.
next prev parent reply other threads:[~2023-05-25 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 2:33 [PR PATCH] " sgn
2023-05-25 2:37 ` Vaelatern
2023-05-25 2:39 ` Vaelatern
2023-05-25 2:43 ` Vaelatern [this message]
2023-06-07 13:49 ` zdykstra
2023-06-07 13:54 ` zdykstra
2023-06-08 5:42 ` [PR PATCH] [Closed]: " sgn
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=20230525024357.g97IM2uddewC3DL3IIESx2COS4IBAE764OfzzCzgAx0@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).