Linux 4.9 is out

Post by ajdlinux » Mon, Dec 12, 2016, 1:09 AM UTC

anarazel wrote: post #3

mparlane wrote: post #2

The amount of times the word "updates" appears in the commits makes me feel much better at my difficulty of choosing succinct and unique commit messages.

Note that those aren't "change commits", but merge commits aggregating large swathes of other changes. And it's not even all merge commits, it's just the merges from Linus' "top lieutenants". But I sympathize. I often spend more time on commit messages than the actual changes...

Post by voltagex_ » Mon, Dec 12, 2016, 1:43 AM UTC

ajdlinux wrote: post #23

The Kernel Newbies LinuxChanges page hasn't been updated yet, but when it is, it'll be at https://kernelnewbies.org/LinuxChanges .

Post by koolba » Mon, Dec 12, 2016, 3:29 AM UTC

ajdlinux wrote: post #22

anarazel wrote: post #3

Earlier quoted context omitted.

Note that those aren't "change commits", but merge commits aggregating large swathes of other changes. And it's not even all merge commits, it's just the merges from Linus' "top lieutenants". But I sympathize. I often spend more time on commit messages than the actual changes...

Indeed - when you go and look at the individual commits, the commit messages tend to be a lot more complex :) My worst commit-message-to-code-changed ratio is a commit in the kernel with a 1307 char/175 word commit message, and a single character change...

Post by voltagex_ » Mon, Dec 12, 2016, 3:40 AM UTC

wtallis wrote: post #25

voltagex_ wrote: post #21

Still no sign of NVMe "RAID" support: http://marc.info/?t=147709622400002&r=1&w=2

There's already a patch (due for 4.10) to detect and warn about this silliness. Since the Intel guy says that all the systems that shipped with this mode now have firmware updates to allow disabling it, there's very little reason for anyone to implement full support. Hopefully in the future Intel will think twice before implementing ugly firmware-level hacks to aid in working around limitations of Microsoft's driver…

Post by ajdlinux » Mon, Dec 12, 2016, 4:03 AM UTC

koolba wrote: post #26

ajdlinux wrote: post #22

Earlier quoted context omitted.

Indeed - when you go and look at the individual commits, the commit messages tend to be a lot more complex :) My worst commit-message-to-code-changed ratio is a commit in the kernel with a 1307 char/175 word commit message, and a single character change...

Arguably you could frame that as "best". Link for the curious?