Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Linux 6.5 (iu.edu)
76 points by mfiguiere on Aug 28, 2023 | hide | past | favorite | 14 comments


Please use the official mailing list archive (lore.kernel.org). The others are much worse (and non-official).


Agreed. While I like my school getting some pub on HN, it's not the original source.



Can anybody add context on why this is newsworthy? The linked email isn't very informative. Is there an awaited new feature in 6.5 that makes this email (which is not even an actual announcement of the release) noteworthy?


You're right, for the layman it's a pretty boring announcement, but that's how Linus has always done all releases so for people who know, it's not a surprise.

The Linux development ecosystem is extremely tightknit with a lot of people working on various different things, and unless you're using the Kernel for a specific thing, then yeah - none of the logs, shortlogs and release files are going to make any sense, because for the most part - they don't make any sense for anyone who isn't specifically using that part of the Kernel personally.


Looks like the fix for the 34% regression made it in.

Feng Tang (1): x86/fpu: Set X86_FEATURE_OSXSAVE feature after enabling OSXSAVE in CR4

https://www.phoronix.com/news/Linux-6.5-x86-Fix-34p-Drop


Note this fixes a regression introduced by 6.5, so it's of no relevance to anyone except people running 6.5 RC kernels.


For 6.6 I'll be eagerly watching for bcachefs maybe being mainlined.


I know right? I love zfs but i want something with a better licence and for that filesystem to be in mainline for the decade it will take for me to be comfortable with its maturity it needs to get started ASAP, otherwise i will probably die before i can switch.


Interesting to see that this website is hosted from Indiana.edu. Does Linus have an affiliation with the university?


This is just a mirror of the official list, AFAIK.


When Linus says, "let's give it one last round of testing", what happens?


> I already have ~20 pull requests pending and ready to go, but before we start the next merge frenzy, please give this final release one last round of testing, ok?

It means that Linux is holding off for a few days on starting the 6.6 release cycle, so that late issues can possibly be fixed before everyone's focus is captured again by the next release.

Usually that means awaiting the build results and self-tests from the distributions (although many will have already done that on the -rc kernels).


I don't know. But my feeling is rather few people test. Of course there is some automatic testing. That probably continues until the next rc1 is out?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: