Gahhh. Ignore most of that stuff about language, it doesn't add much value. Just use common sense: Be clear, be informative, don't waste people's time. You're

Gahhh. Ignore most of that stuff about language, it doesn't add much value. Just use common sense: Be clear, be informative, don't waste people's time. You're not writing deathless prose or trying to craft the Greatest Commit Comment of All Time. The Grammar Police are not going to break down your door with their milspec copies of Strunk and White and put you up on charges. One thing I try to do is be a little entertaining. Just little things, a twist of a phrase or something that might cause a commit to stick in someone's head for a while. I've had comments like "Best commit logs of the project," so at least people were looking forward to reading them. Which, if you are scientific and dry and oh-so-grammarly-correct, they won't be. I've had people mention some source-code comments I'd made a decade or two earlier (e.g., in public headers). That was fun.