For me, it's all about understanding context of a change, the "why" (commit message) not "what" (code comments).
I can run regression tests to find where things broke and, with the messages, have a good understanding of the context and mindset the developer was working in.
In my editor, I can select some code and click "show history for selection" and get a complete log of what happened on those lines. If the commit messages are good, I'll have on understanding of the context of the change.
Missing commit messages usually result in "I don't remember" type emails from the author when I inevitably ask what them why they made a change.
For me, it's all about understanding context of a change, the "why" (commit message) not "what" (code comments).
I can run regression tests to find where things broke and, with the messages, have a good understanding of the context and mindset the developer was working in.
In my editor, I can select some code and click "show history for selection" and get a complete log of what happened on those lines. If the commit messages are good, I'll have on understanding of the context of the change.
Missing commit messages usually result in "I don't remember" type emails from the author when I inevitably ask what them why they made a change.