Linux kernel 要发布 5.0 了。。

跟原因是 linus 认为 4.21的小版本号太多了。。。

邮件内容如下：

https://lore.kernel.org/lkml/20190107160756.7c502d5a@canb.auug.org.au/T/

From: Linus Torvalds @ 2019-01-07  2:14 UTC (permalink / raw)  To: Linux List Kernel MailingSo this was a fairly unusual merge window with the holidays, and as aresult I'm not even going to complain about the pull requests thatended up coming in late. It all mostly worked out fine, I think. Andlot of people got their pull requests in early, and hopefully had acalm holiday season. Thanks again to everybody.The numbering change is not indicative of anything special. If youwant to have an official reason, it's that I ran out of fingers andtoes to count on, so 4.21 became 5.0. There's no nice git objectnumerology this time (we're _about_ 6.5M objects in the git repo), andthere isn't any major particular feature that made for the releasenumbering either. Of course, depending on your particular interests,some people might well find a feature _they_ like so much that theythink it can do as a reason for incrementing the major number.So go wild. Make up your own reason for why it's 5.0.Because as usual, there's a lot of changes in there. Not because thismerge window was particularly big - but even our smaller merge windowsaren't exactly small. It's a very solid and average merge window withjust under 11k commits (or about 11.5k if you count merges).The stats look fairly normal. About 50% is drivers, 20% isarchitecture updates, 10% is tooling, and the remaining 20% is allover (documentation, networking, filesystems, header file updates,core kernel code..). Nothing particular stands out, although I do likeseeing how some ancient drivers are getting put out to pasture(*cought*isdn*cough*).As usual even the shortlog is much too big to post, so the summarybelow is only a list of the pull requests I merged.Go test. Kick the tires. Be the first kid on your block running a 5.0pre-release kernel.              Linus