News for hackers. Stuff that matters.
Re:Intel SA-00145: Lazy FP State Restore by hinkley on Wednesday June 13, 2018 @08:25PM (#17308230)
Contrast this with the Postgres addon community, which has a culture of pushing changes upstream until they no longer have to maintain a fork of the Postgres code.

Build a business on a fork, then compartmentalize it until it can run without modifying the core so you can get off the bugfix treadmill.

Re:Intel SA-00145: Lazy FP State Restore by dralley on Wednesday June 13, 2018 @10:05PM (#17308683)
The changes are all upstream to begin with.

It's a fork in the sense that it's heavily diverged from the source of the old kernel, but it's all still backports and not a ton of new development.

Re:Intel SA-00145: Lazy FP State Restore by hinkley on Thursday June 14, 2018 @02:07AM (#17309667)
Why does it need to be diverged if there is no new functionality in their version? Because they can?
Re:Intel SA-00145: Lazy FP State Restore by kikoreis on Thursday June 14, 2018 @04:56AM (#17310349)
ABI stability to support binary-only loadable modules is probably the most important reason.
Re:Intel SA-00145: Lazy FP State Restore by vertex-four on Thursday June 14, 2018 @03:39AM (#17310063)
Why do many distros have releases to which only bug and security fixes are applied? Same reason. The divergence is just those fixes.