Changes between Version 4 and Version 5 of CodingTips

Timestamp:

2018-02-24T20:07:10Z (6 years ago)

Author:

Jakub Jermář

Comment:

Update for Git

CodingTips

@@ -9 +9 @@
     * Doxygen and regular comments
  * Adhere to RCS rules from the very beginnning
-    * Use Bazaar for revision control
+    * Use Git for revision control
     * Separate into reasonably-sized changesets
-    * Changeset comments must be complete, descriptive English sentences, typically in infinitive/imperative tense
+    * Make sure that each commit is accompanied by a commit message that follows the example below. The first line should be a short description of WHAT the commit does written in imperative mood. It should not exceed 50 columns of text width and the trailing period should be omitted. The next line should be empty. Optionally, you may provide additional paragraphs that explain WHY the change was made. The text should not exceed 72 columns of width. Note that some editors will help you follow these rules by text highlighting. The entire commit message must be written in English.
 {{{
-Example: Fix DNS resolution not working due to missing local address.
-}}}
+Make INTERFACE_LOC_SUPPLIER parallel
+    
+Location service sometimes needs to be able to process requests in
+parallel in order to avoid deadlock.
+}}} 
 
 == Recommended coding practices ==