and don't have autoconf installed. They'll be unable to make without playing
around with `touch'.
-The correct order to commit the configure-related files is:
+The correct procedure to commit the configure-related files is:
-% cvs commit acconfig.h aclocal.m4 config.h.in configure.in configure stamp-h.in
+ % cvs commit acconfig.h aclocal.m4 configure.in
+ % autoconf && autoheader
+ % cvs commit config.h.in configure
+ % make stamp-h.in
+ % cvs commit stamp-h.in
-If you haven't changed all of those files, just commit the rest in the
-stated order (e.g. cvs commit acconfig.h config.h.in stamp-h.in).
+If you haven't changed all of those files, just commit the rest in the stated
+order (e.g. cvs commit acconfig.h config.h.in stamp-h.in). The reason for
+the sequence is the RCS Id strings in the edited files -- they change when
+you commit the changes.
+
+You can run just "make" instead of the other commands in between cvs commits.
-------------------
"time". Date and time manipulation routines go here.
+-------------------------------------------------------
+nmh-local functions to use in preference to OS versions
+-------------------------------------------------------
+
+For some system functions whose availability or behavior varies from OS to OS,
+nmh conditionally uses a local definition with the same name as the OS function
+(e.g. snprintf()). For other functions, developers need to avoid the OS
+versions and always use the nmh-supplied function. Here is a list of such
+functions:
+
+OS function nmh-local version to use instead
+=========== ================================
+getpass() nmh_getpass()
+
+
-------------
releasing nmh
-------------