I really appreciate this kind of commit message. There’s some very good ones in the Mercurial logs too: https://www.mercurial-scm.org/repo/hg/rev/3764330f76a6

I really appreciate this kind of commit message. There’s some very good ones in the Mercurial logs too: https://www.mercurial-scm.org/repo/hg/rev/3764330f76a6 https://www.mercurial-scm.org/repo/hg/rev/3764330f76a6 https://www.mercurial-scm.org/repo/hg/rev/93486cc46125 https://www.mercurial-scm.org/repo/hg/rev/93486cc46125 https://www.mercurial-scm.org/repo/hg/rev/b7a966ce89ed https://www.mercurial-scm.org/repo/hg/rev/b7a966ce89ed https://www.mercurial-scm.org/repo/hg/rev/4a0d0616c47d https://www.mercurial-scm.org/repo/hg/rev/4a0d0616c47d (all modesty aside) Long commit messages aren’t that atypical. Have a stroll through the logs: https://www.mercurial-scm.org/repo/hg/log?style=gitweb https://www.mercurial-scm.org/repo/hg/log?style=gitweb Mercurial inherited this style of commit messages from Linux email-based code review (the Mercurial originator was a kernel hacker), because in that workflow your commit messages are kind of a persuasive essay for why your commit should be accepted. I believe that writing commit messages with that kind of goal in mind, thinking “why should you take this commit?” is a good motivator for writing something good and useful.