I love descriptive git commit messages. For those complaining about the length:
1) Just read the title
2) Maybe have TL;DR section for a summary, and details for who cares.
3) Use pretty printing for git log
Having a rich commit message is extremely important for capturing code review discussions and design decisions and glue things together for the set of changes in a single place. The advantages far outweigh any negatives from a short commit message that will not give you the "why" of the solution.
Having a rich commit message is extremely important for capturing code review discussions and design decisions and glue things together for the set of changes in a single place. The advantages far outweigh any negatives from a short commit message that will not give you the "why" of the solution.