Trying to impose "one way" to write commit messages is silly at best.

At work I follow whatever convention the team I'm on agrees with.

For my projects I use commit messages as a way to "tag" changes, more than to explain the changes using prose. That way it's very easy for me to search for changes in the codebase.

eg. #event-loop #fix #multiple-dispatch #repeated-message (remove the # and you get the idea)