[tor-commits] [tor/master] remove EOL at EOF advice
nickm at torproject.org
nickm at torproject.org
Mon Jun 18 20:18:47 UTC 2018
commit 9af6c48d24ccc38d8e9301a208dddc8695fe63c6
Author: Nick Mathewson <nickm at torproject.org>
Date: Mon Jun 18 16:18:44 2018 -0400
remove EOL at EOF advice
---
doc/HACKING/CodingStandards.md | 2 --
1 file changed, 2 deletions(-)
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index 4a8f13716..b830ecea9 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.
-
More information about the tor-commits
mailing list