diff options
| author | Thien-Thi Nguyen <ttn@gnuvola.org> | 2010-02-09 14:29:36 +0100 |
|---|---|---|
| committer | Ludovic Courtès <ludo@gnu.org> | 2010-02-13 23:51:07 +0100 |
| commit | 60b6a84f0f2d8d43491835a518463f4a8273bf87 (patch) | |
| tree | f346dc6ecdfaf836ec7b90e820bd547bf13d7cd0 /HACKING | |
| parent | 4adf9a7e2750593e444a2c7d950e194294242896 (diff) | |
Document trailing whitespace policy.
* HACKING (Coding standards): Delete trailing whitespace.
Add blurb documenting trailing whitespace policy.
Signed-off-by: Thien-Thi Nguyen <ttn@gnuvola.org>
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -230,7 +230,7 @@ When deprecating a definition, always follow this procedure: - Write commit messages for functions written in C using the functions' C names, and write entries for functions written in Scheme -using the functions' Scheme names. For example, +using the functions' Scheme names. For example, * foo.c: Moved scm_procedure_documentation from eval.c. @@ -278,6 +278,9 @@ the list of years in the copyright notice at the top of the file. - When you get bug reports or patches from people, be sure to list them in THANKS. +- Do not introduce trailing whitespace (and feel free to clean it up +opportunistically, that is, if doing so is part of some other change). +The goal is to reduce (and over time, eliminate) spurious diffs. Naming conventions ================================================= |