Conversation
Notices
-
Am I the only one in the world who is deeply !disturbed and #annoyed with empty commit messages? I write screenfuls of commit notes!
-
why in the world did empty commit messages when we have http://whatthecommit.com/ ?
Windigo | ☴ likes this. -
@bkuhn no :(
-
@bkuhn gah, don’t get me started, I write descriptive commit messages, I break commits into atomic changesets, then they are ignored :(
-
@fontana assuming trolling but answering anyway. The commit log should have this information, even if it is obvious when looking at code.
-
Given that the most common way to see commit messages is on their own (via “git log”, or Gitorious’s commit timeline, or Github’s ..
-
.. “latest commit” box), with no accompanying diff, it should be common courtesy to explain even that which is obvious in the diff.
-
Those 3 examples are all git-based, as I use git, but my limited experience with other VCSes suggests no-diff display of commits is common.
-
I believe the commit message should help reader understand the state of mind of the commiter at time of the commit. Important historically.
-
@kevingranade Not #troll‘ing but in my limited use of VCSes often find most appropriate message would be “Nothing important” cc: @bkuhn
-
@fontana Perhaps you should start making important updates?
-
@bkuhn perhaps a “state of mind” flag of some sort is called for then
-
@reality Fair enough
-
@fontana, the really !disturbing fact here is that you don’t often use VCS’s. I use one for all documents of any importance. Why don’t you?
-
All Micro.Fragdev.com content and data are available under the