summaryrefslogtreecommitdiff
path: root/doc/HACKING
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2018-06-18 16:18:44 -0400
committerNick Mathewson <nickm@torproject.org>2018-06-18 16:18:44 -0400
commit9af6c48d24ccc38d8e9301a208dddc8695fe63c6 (patch)
tree9ae66766d7ca177abfd4d8639e7e069942515834 /doc/HACKING
parent67dc83fa75e2009b4b6bd5d7f005adcaf45d0c77 (diff)
downloadtor-9af6c48d24ccc38d8e9301a208dddc8695fe63c6.tar.gz
tor-9af6c48d24ccc38d8e9301a208dddc8695fe63c6.zip
remove EOL@EOF advice
Diffstat (limited to 'doc/HACKING')
-rw-r--r--doc/HACKING/CodingStandards.md2
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index 4a8f13716b..b830ecea93 100644
--- a/doc/HACKING/CodingStandards.md
+++ b/doc/HACKING/CodingStandards.md
@@ -172,7 +172,6 @@ deviations from our C whitespace style. Generally, we use:
- Unix-style line endings
- K&R-style indentation
- No space before newlines
- - A blank line at the end of each file
- Never more than one blank line in a row
- Always spaces, never tabs
- No more than 79-columns per line.
@@ -437,4 +436,3 @@ the functions that call your function rely on it doing something, then your
function should mention that it does that something in the documentation. If
you rely on a function doing something beyond what is in its documentation,
then you should watch out, or it might do something else later.
-