I think long messages are a good habit. Start with something readable in the history, past that who cares? Most people rarely read past the preview, and if they do they want details
I think it's great because it makes you reflect on what the goal was and what you did. I sometimes stop to make a quick change as I'm writing, or just collect my thoughts before mentally dismissing the task
I had just figured out how to fix a bug that broke our in house reminder system. My smug ass put hoho as the commit message for figuring something out that the previous guy couldn't. Of course it came back to bite me in the ass THIS WEEK when the system broke again in a similar fashion, but I couldn't remember what I had done.
Added zip code to the reseller portal when batch-creating transactions in <main-project>
I try to start off descriptive, in case I want to diff a few changes back. After that, sometimes I write notes or general reflections on life in there... Until yesterday I thought no one was reading them
