[tobr]

This seems very sensible, and completely at odds with the common “best practice” of keeping commit messages short. I find that the best way to understand why a piece of code is the way it is is not through comments in the code, but by looking at history and commit messages. They are comments where it’s completely clear what code they describe, even if it’s spread out across the code base, and even if the code has since been changed to the point where the comment is no longer applicable.

[UK-AL]

Commit titles should be short.

Commit messages are often small essays. Especially in the Linux kernel

[gunnihinn]

Yeah. I’ve never been unhappy with reading a long commit message.