Changes between Version 1 and Version 2 of Development/Commits

Timestamp:

10/30/10 17:40:58 (3 years ago)

Author:

stuge

Comment:

--

Development/Commits

@@ -1 +1 @@
 = Commit messages =
 
-It's important to write good commit messages that will stand the test of time, so that those who review your patches can know what the patch is supposed to do, and so that anyone looking back at the repository history can see what was done.
+It's important to write good commit messages that will stand the test of time, so that those who review your patches can know what the patch is supposed to do, and so that anyone looking at the repository history (e.g. when tracking down a regression) can see what was done in the past.
 
 == General format ==
@@ -8 +8 @@
 Short one line description of commit, preferably <= 60 chars
 
-This is line 3 where a long description of the commit can start. The
-description should normally include some background on why this commit
-was required and why it is best that the commit changes things the way
-it does. Lines should preferably be <= 70 characters. Note that line 2
-should be left blank.
+This is line 3 where a long description of the commit can start. Line 2
+above should always be left blank. The long description should normally
+include some background on why this commit was required and why it is
+best that the commit changes things the way it does. Lines should
+preferably be <= 70 characters.
 }}}