X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=docs%2FREADME.developers;fp=docs%2FREADME.developers;h=fe3135244c63c8a337d7a7b6edcfb9160b4a74b4;hp=14cf138e3a489464b3f40d36672f2615f339f277;hb=73b48d6c0c6ed51bcf0f3b3388ffc6beb372c4c5;hpb=ad5121f68a2d40e9a0ee2eedcd49700085648227

diff --git a/docs/README.developers b/docs/README.developers
index 14cf138..fe31352 100644
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -44,7 +44,7 @@ around with `touch'.
 The correct procedure to commit the configure-related files is:
 
     % cvs commit acconfig.h aclocal.m4 configure.in
-    % autoheader; autoconf; date > stamp-h.in
+    % autoheader; autoconf; \date > stamp-h.in
     % cvs commit config.h.in configure stamp-h.in
 
 The reason for the three-step commit is that configure.in contains the RCS $Id
@@ -53,7 +53,8 @@ the autoconf regeneration should be held off until after the commit, or your
 local stamp-h.in will become out-of-sync with the CVS version (granted, not that
 big a deal).  For the second step, you're doing the same commands as a 
 `make reset' would do, but using that command would require extra configure runs
-to make Makefile be up-to-date.
+to make Makefile be up-to-date.  The reason for the backslash on `date' is in
+case you have `date' aliased in your shell to use a nonstandard format.
 
 If you haven't changed all the files noted above, just commit the ones you have
 changed, in the stated order (for instance, configure.in, then configure and