() l...@gnu.org (Ludovic Courtès) () Sat, 23 Jan 2010 17:10:50 +0100 To me it’s clear: status quo, i.e., no ‘whitespace-cleanup’ or similar all around, but encourage people not to leave trailing whitespace.
OK, thanks for the clarification. Please find attached a patch to HACKING. thi
>From 893dfb5d11e6d2ae6ff56492741711ec368257a4 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen <t...@gnuvola.org> Date: Tue, 9 Feb 2010 14:29:36 +0100 Subject: [PATCH] Document trailing whitespace policy. * HACKING (Coding standards): Delete trailing whitespace. Add blurb documenting trailing whitespace policy. Signed-off-by: Thien-Thi Nguyen <t...@gnuvola.org> --- HACKING | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/HACKING b/HACKING index ffe04a8..7463fe5 100644 --- a/HACKING +++ b/HACKING @@ -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 ================================================= -- 1.6.3.2
