Skip to content

Commit

Permalink
Writing_Good_Commits: Improve reasoning
Browse files Browse the repository at this point in the history
  • Loading branch information
@sils
sils committed May 28, 2015
1 parent e5cb2ba commit c35c117
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions doc/Getting_Involved/Writing_Good_Commits.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ commit message.
the key to developing good software and finding its bug before they occur.
* Good commit messages make it easy to check at a glance what happened in a
time range.
* It is way easier to revert single changes without side effects. Reverting
multiple commits at a time is easy, reverting a part of a commit is not.
* `git blame` will be much more effective. It is the best documentation you
can get. The older your code is, the more documentation it has. The better
the commit messages are, the better is your hidden documentation. Your
Expand Down

1 comment on commit c35c117

@zeenix
Copy link

@zeenix zeenix commented on c35c117 May 28, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Please sign in to comment.