Nothing particularly odd going on this merge window. I had some travelin the middle of it, but to offset that I had a new faster test-buildsetup, and most of the pull requests came in early (thank you) so mytravels didn't actually end up affecting the merge window all thatmuch.We did have a few late pull requests too, but since that meshed fairlywell with my schedule as per above, and people generally made theproper noises ("sorry for late pull request, I had good reasons: xyz")I didn't mind this time. But let's try to not repeat that, ok?Things look fairly normal. Just about two thirds of the patch isdrivers (all over), with the bulk of the rest being arch updates,tooling, documentation and vfs/filesystem updates, of which there weremore than usual (the unicode tables for ext4 case insensitivity do endup being a big part of the "bulk" side).But there's core networking, kernel and vm changes too - it's justthat the other areas tend to simply be much bulkier. Drivers etc tendto just have a ton more lines to them, if only by virtue of therebeing so many of them (although admittedly also sometimes because somedrivers tend to just be very verbose and have a lot of registerdefinitions etc).Size-wise things look fairly normal. 12k+ commits (plus another ~750merge commits) is about normal for us by now. And hard to summarize ina release email. So appended is obviously just the usual shortlog ofmerges I did and their sources, for a kind of overview of the _areas_that have changed, rather than any real detail. You'll need to go lookat the git tree to see the details.Go forth and test, Linus
|
|