Re:Omniref (YC W15) Is Rap Genius for Code
by grandalf on Thursday January 01, 2015 @12:34PM
(#8823531)
I think for practical purposes there would ideally be a convention for the high level aspect of a commit message and the details...
Though the counter-argument is to commit exactly when a single reasonable commit message contains enough information... squashing defeats this.
That said, is there a such thing as a commit message too long? If I were to include the thinking behind code I would have some commit messages over 500 lines long.
Currently I just create an Evernote note for each change I make, which documents all the whys, the research, the issues, pros/cons, etc. with a given change. The commit message usually gets a much briefer version of it.