=== chris14_ is now known as chris14
=== JanC_ is now known as JanC
=== UnivrslSuprBox_ is now known as UnivrslSuprBox
=== klebers_ is now known as klebers
[13:11] <nibbon_> o/
[13:12] <nibbon_> is there a way to be sure this commit https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=e8104b224c3d60a0f384f6b38419523aed4912dd landed in 5.15.0-97-generic?
[13:12] -ubottu:#ubuntu-kernel- Commit e8104b2 in ~ubuntu-kernel/ubuntu/+source/linux/+git/jammy "NFSv4.1: fixup use EXCHGID4_FLAG_USE_PNFS_DS for DS server"
=== halves7 is now known as halves
[16:51] <mdiewa> nibbon_: that commit is not in 5.15.0-97-generic. It landed in 5.15.0-100-generic. If you wanted to check for yourself, you would checkout tag Ubuntu-5.15.0-97.107 and look for the commit in its log. Alternatively you could check the changelog for the package here: https://launchpad.net/ubuntu/+source/linux/5.15.0-97.107
[16:53] <nibbon_> mdiewa: what confused me it's seeing it in 5.15.0-96 https://paste.debian.net/1311415/
[16:53] <nibbon_> but likely -96 was never released
[16:53] <mdiewa> nibbon_: Correct.
[16:55] <nibbon_> mdiewa: alright, thanks for the confirmation
=== JanC_ is now known as JanC
[21:36] <arraybolt3> Quick question, I know that there are some features of Ubuntu (like encrypted /boot support in GRUB) that are not officially supported code paths and are to be steered clear of. I'm wondering, is BTRFS's built-in compression features something that the Ubuntu Kernel team would consider a supported use case, or is that one of those unsupported code paths?
[23:27] <sarnold> i'm not on the kernel team but I'd expect compression to be fine. stay away from the raid5-ish modes.