X-Git-Url: http://git.marmaro.de/?a=blobdiff_plain;f=docs%2FREADME.developers;h=fe3135244c63c8a337d7a7b6edcfb9160b4a74b4;hb=19b47ea980a98d01112d4bda1d220c7057818ff1;hp=44000710f6baf22d3d87bf9bc631c82c4b0215d1;hpb=7379ff1546ba2feaabe8b6463f448ea0bafd69bb;p=mmh

diff --git a/docs/README.developers b/docs/README.developers
index 4400071..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
@@ -171,10 +172,12 @@ To make a public release of nmh (we'll use version 1.0.4 and my mhost.com
 account, danh, as examples here):
 
  1. % echo 1.0.4 > VERSION
+    % date +"%e %B %Y" > DATE
+    (DATE should contain something like "30 December 2000")
 
  2. Put a comment like "Released nmh-1.0.4." in the ChangeLog.
 
- 3. % cvs commit ChangeLog VERSION
+ 3. % cvs commit ChangeLog VERSION DATE
 
  4. % cvs tag nmh-1_0_4
     (cvs treats dots specially, so underscores are substituted here.)