From 73b48d6c0c6ed51bcf0f3b3388ffc6beb372c4c5 Mon Sep 17 00:00:00 2001 From: Dan Harkless Date: Tue, 6 Feb 2001 04:28:04 +0000 Subject: [PATCH] Say in README.developers to use `\date' in case anyone is like me and has `date' aliased in their shell to use a nonstandard (but subjectively more readable) format. --- ChangeLog | 6 +++++- docs/README.developers | 5 +++-- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index d38ffc3..47a679e 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,4 +1,4 @@ -Mon Feb 05 19:39:06 2001 Dan Harkless +Mon Feb 05 20:22:54 2001 Dan Harkless * -L isn't sufficient for specifying the path of the Cyrus SASL shared library. That'll allow us to link successfully, but on @@ -11,6 +11,10 @@ Mon Feb 05 19:39:06 2001 Dan Harkless * Print whether we have SASL support in the "nmh configuration" summary configure prints out. + * Say in README.developers to use `\date' in case anyone is like + me and has `date' aliased in their shell to use a nonstandard (but + subjectively more readable) format. + Thu Jan 25 21:15:52 2001 Shantonu Sen * man/mh-chart.man has updated synposes of 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 -- 1.7.10.4