SoylentNews is people
SoylentNews
OMG! Ubuntu! reports
The arrival of the Linux Kernel 4.12 at the weekend brought a boat load of big changes (including two I/O schedulers) but do you know how big it is?
Well, it's easy to see in this chart shared by kernel maintainer Greg Kroah-Hartman which details exactly how big the release is. graphic
"Linux 4.12 is big, really big, like bigger than you thought big", [Greg] says in an update on his Google+ profile.
It took 63 days to create Linux 4.12, during which a total of 14,570 commits were made across 59,806 files.
With 24,170,860 [...] lines of code in the Linux kernel 4.12, that works out at a boggling 795.58 lines of code added per hour.
Linus Torvalds commented on the size of the latest stable release in his mailing list post to announce the release, saying:
"As mentioned over the various rc announcements, 4.12 is one of the bigger releases historically, and I think only 4.9 ends up having had more commits [...] 4.12 is just plain big."
(Score: 0) by Anonymous Coward on Saturday July 08 2017, @02:09AM (8 children)
Big != Good
(Score: 0) by Anonymous Coward on Saturday July 08 2017, @02:11AM (4 children)
Big != Bad
(Score: 3, Insightful) by kaszz on Saturday July 08 2017, @02:17AM (3 children)
Seems you believe in luck ;-)
Big means big chance of more bugs than for less code.
(Score: 4, Insightful) by frojack on Saturday July 08 2017, @04:41AM (2 children)
Exactly. Where are all these sets of eyes that are supposed to be Reading all this code?
If each of us able to to read and comprehend enen the simplest module were to adopt one single program, we still couldn't even gloss through the kernel and drivers, and almost certainly couldn't find any significant errors.
Lots of code is lots of problems.
No, you are mistaken. I've always had this sig.
(Score: 2) by kaszz on Saturday July 08 2017, @11:50AM
In other words, simple and small code is good code (usually).
(Score: 2) by http on Saturday July 08 2017, @06:16PM
That's a wild misinterpretation of the Linus's Law (coined by ESR), which is "Given enough eyeballs, all bugs are shallow."
Nowhere does it say everyone has to read the code, or even that they should, or even that it's a good idea. Or even most coders on a project. The point Raymond was underlining is that with open code, it's easy to collaborate and find the origin of a particular bug. This task is at right angles to both auditing commits and fixing bugs.
I browse at -1 when I have mod points. It's unsettling.
(Score: 0) by Anonymous Coward on Saturday July 08 2017, @02:13AM (1 child)
You just keep tellin' 'em that.
(Score: 1, Troll) by Ethanol-fueled on Saturday July 08 2017, @06:55AM
Fucking Niggers.
(Score: 1, Touché) by Anonymous Coward on Saturday July 08 2017, @02:13AM
You realize you don't need to select "yes" for every option and every driver in the config?