News for hackers. Stuff that matters.
Re:How to Write a Git Commit Message by divan on Sunday September 13, 2015 @05:28PM (#10212849)
Does the majority read commit messages as "If applied, this commit will..."?

I always treated log messages as a history of events, i.e. describing what had happened in the past - this commit "fixed" something, and this one "changed" something, "refactored", "implemented", etc.

Re:How to Write a Git Commit Message by nanny on Monday September 14, 2015 @10:41AM (#10215283)
The "use the imperative mood" trope has gotten completely out of hand, and the "If applied, this commit will ..." argument is entirely nonsensical. You can slightly adjust the lead-in and make the same exact argument for a different tense, e.g., simply take "will" out of the sentence and you have the same argument for the present tense.

The most important thing is to discuss it with your team and consistently use the tense chosen.

Re:How to Write a Git Commit Message by seiji on Sunday September 13, 2015 @05:43PM (#10212893)
A commit object is a container talking about itself. You don't talk about your present state in the past tense.
Re:How to Write a Git Commit Message by GavinMcG on Sunday September 13, 2015 @06:10PM (#10212963)
A commit object is a container of changes. A commit message is a label placed on that container by whoever packed it. It's not the container talking about itself – it's a programmer labeling something for other programmers to read (in the future) about something they have already done.
Re:How to Write a Git Commit Message by jarfil on Monday September 14, 2015 @03:47AM (#10214005)
That would be the egocentric view, instead of letting the commit stand on its own.
Re:How to Write a Git Commit Message by donatj on Sunday September 13, 2015 @07:20PM (#10213105)
I've generally taken the tone of what the commit does "Fixes widget 22", "Adds foo bar"