Browse Source

remove EOL@EOF advice

Nick Mathewson 6 years ago
parent
commit
9af6c48d24
1 changed files with 0 additions and 2 deletions
  1. 0 2
      doc/HACKING/CodingStandards.md

+ 0 - 2
doc/HACKING/CodingStandards.md

@@ -172,7 +172,6 @@ deviations from our C whitespace style.  Generally, we use:
    - Unix-style line endings
    - Unix-style line endings
    - K&R-style indentation
    - K&R-style indentation
    - No space before newlines
    - No space before newlines
-   - A blank line at the end of each file
    - Never more than one blank line in a row
    - Never more than one blank line in a row
    - Always spaces, never tabs
    - Always spaces, never tabs
    - No more than 79-columns per line.
    - 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
 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,
 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.
 then you should watch out, or it might do something else later.
-