summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorLeif Madsen <leif@leifmadsen.com>2009-03-27 19:31:04 +0000
committerLeif Madsen <leif@leifmadsen.com>2009-03-27 19:31:04 +0000
commitd000310a2a35f3a5bf705f90877a48ac37154592 (patch)
treed62a77dac95e1b709ebf9722a29334848db11617 /include
parent9381bff79d8c042affb23d3733fe6aa272a1f579 (diff)
Update commit message guidelines in re: to punctuation.
The doxygen documentation has now been updated to state explicitly that I want punctuation atthe end of the first sentence in a commit message. :). git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@184798 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'include')
-rw-r--r--include/asterisk/doxyref.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/include/asterisk/doxyref.h b/include/asterisk/doxyref.h
index f459a1afc..f58dd8cfc 100644
--- a/include/asterisk/doxyref.h
+++ b/include/asterisk/doxyref.h
@@ -360,7 +360,8 @@
* Some commit history viewers treat the first line of commit messages as the
* summary for the commit. So, an effort should be made to format our commit
* messages in that fashion. The verbose description may contain multiple
- * paragraphs, itemized lists, etc.
+ * paragraphs, itemized lists, etc. Always end the first sentence (and any
+ * subsequent sentences) with punctuation.
*
* Commit messages should be wrapped at 80 %columns.
*