News for hackers. Stuff that matters.
Re:Comparing Git Workflows by lmm on Friday May 27, 2016 @06:11AM (#11784990)
Commit messages are very rarely read. I'd say it's well worth committing anything that compiles (that can only help bisection, which is a much more important use for history than human readability). Even a non-compiling commit isn't really a hindrance - if it doesn't compile mark it as unknown (you're using an automated bisect script that does that, right?), and you end up with the same result as if that commit hadn't been made.
Re:Comparing Git Workflows by justincc on Friday May 27, 2016 @08:13AM (#11785460)
I am always reading commit messages to find out why such -and-such a thing changed. I agree that making frequent commits is really great but I always want to see every commit have a meaningful message, either at the time it is made or in cleanup before pushing to the remote branch.