News for hackers. Stuff that matters.
Re:How to Write a Git Commit Message by aikah on Sunday September 13, 2015 @07:29PM (#10213118)
> more than one atomic change into a single commit

There is no such thing as an "atomic change". Sometimes, fixing a single bug ,adding a single feature requires the edition of multiple files or even complex changes. I personally don't like these projects with 1 commit per file change ,that's ridiculous and it's noisy.

Re:How to Write a Git Commit Message by gutnor on Sunday September 13, 2015 @07:42PM (#10213144)
I think he mean a single feature.

Like a single commit "Fix bug XYZ", that in reality also contains "Fix typo in error messages", "Change rendering of status page", "Fix test framework DSL to prevent infinite loop".

Naively you could say that each of those should go in their own commit, but reality is that they may actually be quite small and necessary and may not even be seen as a feature by the author or reviewer. Only 6 months down the line, you read the code and wonder why the f*ck there is a change in the test DSL in order to fix bug XYZ.

Re:How to Write a Git Commit Message by nanny on Monday September 14, 2015 @10:36AM (#10215250)
>Sometimes, fixing a single bug ,adding a single feature requires the edition of multiple files

Congrats, that's one atomic change. He didn't say "one commit per file change", he said "one commit per atomic change", and yes, sometimes those atomic changes can spread across multiple files.