guile/guile-core HACKING

[Thien-Thi Nguyen]

CVSROOT:        /cvs
Module name:    guile
Branch:         branch_release-1-6
Changes by:     Thien-Thi Nguyen <address@hidden>       01/11/12 02:23:33

Modified files:
        guile-core     : HACKING 

Log message:
        Restrict documentation change log
        waiver to only apply to ChangeLog files.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile-core/HACKING.diff?cvsroot=OldCVS&only_with_tag=branch_release-1-6&tr1=1.55.2.5&tr2=1.55.2.6&r1=text&r2=text

Patches:
Index: guile/guile-core/HACKING
diff -u guile/guile-core/HACKING:1.59 guile/guile-core/HACKING:1.60
--- guile/guile-core/HACKING:1.59       Sat Sep  1 00:09:05 2001
+++ guile/guile-core/HACKING    Mon Nov 12 02:19:16 2001
@@ -448,12 +448,10 @@
 elements, but we're not changing scm_map at all --- it's appropriate
 to use the Scheme name in the log entry.
 
-- There's no need to keep a change log for documentation files.  This
-is because documentation is not susceptible to bugs that are hard to
-fix.  Documentation does not consist of parts that must interact in a
-precisely engineered fashion; to correct an error, you need not know
-the history of the erroneous passage.  (This is copied from the GNU
-coding standards.)
+- There's no need to keep a change log for a ChangeLog file.  For any
+other kind of file (including documentation, since our documentation
+is indeed precisely engineered -- we surpass GNU standards here), add
+an appropriate ChangeLog entry when you change it.  Simple!
 
 - Make sure you have papers from people before integrating their
 changes or contributions.  This is very frustrating, but very