Jan 07, 2019, 06:00<\/p>\n
(Other stories by Linus Torvalds<\/a>)<\/p>\n So this was a fairly unusual merge window with the holidays, and as a The numbering change is not indicative of anything special. If you<\/p>\n want to have an official reason, it’s that I ran out of fingers and So go wild. Make up your own reason for why it’s 5.0.<\/p>\n Because as usual, there’s a lot of changes in there. Not because this<\/p>\n merge window was particularly big – but even our smaller merge windows The stats look fairly normal. About 50% is drivers, 20% is<\/p>\n architecture updates, 10% is tooling, and the remaining 20% is all As usual even the shortlog is much too big to post, so the summary<\/p>\n below is only a list of the pull requests I merged.<\/p>\n Go test. Kick the tires. Be the first kid on your block running a 5.0<\/p>\n pre-release kernel.<\/p>\n Linus<\/p>\n Complete Story<\/a><\/p>\n Related Stories:<\/p>\n
\nresult I’m not even going to complain about the pull requests that
\nended up coming in late. It all mostly worked out fine, I think. And
\nlot of people got their pull requests in early, and hopefully had a
\ncalm holiday season. Thanks again to everybody.<\/p>\n
\ntoes to count on, so 4.21 became 5.0. There’s no nice git object
\nnumerology this time (we’re _about_ 6.5M objects in the git repo), and
\nthere isn’t any major particular feature that made for the release
\nnumbering either. Of course, depending on your particular interests,
\nsome people might well find a feature _they_ like so much that they
\nthink it can do as a reason for incrementing the major number.<\/p>\n
\naren’t exactly small. It’s a very solid and average merge window with
\njust under 11k commits (or about 11.5k if you count merges).<\/p>\n
\nover (documentation, networking, filesystems, header file updates,
\ncore kernel code..). Nothing particular stands out, although I do like
\nseeing how some ancient drivers are getting put out to pasture
\n(*cought*isdn*cough*).<\/p>\n\n