News for hackers. Stuff that matters.
Re:Linus’s rules on keeping Git history clean (2009) by Cthulhu_ on Wednesday September 04, 2019 @04:39AM (#20875190)
So said log of work is not to be read? Why even bother with commit messages then?

It might not be useful for you or your projects, but that's up to you. Linux is the other side of the coin though - they NEED to be able to read a commit from ten years ago, see what was changed (the diff), why it was changed, and by who it was changed and signed off. Take a look at their repository, e.g. via github for ease of access. Here's a random commit: https://github.com/torvalds/linux/commit/e1e54ec7fb55501c33b.... Even with my complete lack of knowledge of kernel development, I can tell that the minor code change is backed up by a lot of reasoning and intent.

But, it's a wholly different use case. Most applications I've worked with are basically webapps that will be thrown away within five years, where it's not as important.

Re:Linus’s rules on keeping Git history clean (2009) by nomel on Wednesday September 04, 2019 @05:23PM (#20881567)
> Why even bother with commit messages then?

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.