-*-text-*-
Guile Hacking Guide
-Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2008 Free software Foundation, Inc.
+Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2008, 2012 Free software Foundation, Inc.
Permission is granted to anyone to make or distribute verbatim copies
of this document as received, in any medium, provided that the
manage without the deprecated definition.
4. Add an entry that the definition has been deprecated in NEWS and
- explain what do do instead.
+ explain what to do instead.
5. In file TODO, there is a list of releases with reminders about what
to do at each release. Add a reminder about the removal of the
- 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.
- 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.
+
+For Emacs users:
+ (add-hook 'before-save-hook 'delete-trailing-whitespace)
Naming conventions =================================================