[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [tor/maint-0.4.2] CodingStandards: Use consistent spacing



commit eb81704081b92738216f3fadb172f9f55b2b3201
Author: teor <teor@xxxxxxxxxxxxxx>
Date:   Mon Nov 25 12:50:15 2019 +1000

    CodingStandards: Use consistent spacing
    
    * 2 newlines before ====== headers
    * 1 newline before ------ headers
---
 doc/HACKING/CodingStandards.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index e483dd74b..2c273910d 100644
--- a/doc/HACKING/CodingStandards.md
+++ b/doc/HACKING/CodingStandards.md
@@ -42,6 +42,7 @@ If you have changed build system components:
    - For example, if you have changed Makefiles, autoconf files, or anything
      else that affects the build system.
 
+
 License issues
 ==============
 
@@ -58,7 +59,6 @@ Some compatible licenses include:
   - CC0 Public Domain Dedication
 
 
-
 How we use Git branches
 =======================
 
@@ -350,7 +350,6 @@ for more information about trunnel.
 
 For information on adding new trunnel code to Tor, see src/trunnel/README
 
-
 Calling and naming conventions
 ------------------------------
 
@@ -458,7 +457,6 @@ to use it as a function callback), define it with a name like
       abc_free_(obj);
     }
 
-
 Doxygen comment conventions
 ---------------------------
 

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits