Well the wrap of vfork() calls didn't work: its semantics don't allow that. So...

[nmh] / docs / README.developers

diff --git a/docs/README.developers b/docs/README.developers
index 4381a2aba51135d16fb10b141d6957a1cc28e596..2946d8c1b54f5e9a44e6ff60d158deff1d8a3051 100644 (file)
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -16,10 +16,10 @@ autoconf files
 If you wish to change the `configure' script or its related files, you'll need
 to first install GNU m4, available from <ftp://ftp.gnu.org/pub/gnu/m4/> and then
 GNU autoconf (<ftp://ftp.gnu.org/pub/gnu/autoconf/>).  Nmh is currently using
 If you wish to change the `configure' script or its related files, you'll need
 to first install GNU m4, available from <ftp://ftp.gnu.org/pub/gnu/m4/> and then
 GNU autoconf (<ftp://ftp.gnu.org/pub/gnu/autoconf/>).  Nmh is currently using

-a minimum of autoconf 2.54.
+a minimum of autoconf 2.61.

 
 Most of the configure-related files are automatically generated.  The only files
 
 Most of the configure-related files are automatically generated.  The only files

-you should need to manually edit are acconfig.h and configure.in.  Don't, for
+you should need to manually edit are configure.ac and aclocal.m4.  Don't, for

 instance, edit config.h.in.  Though it is an input file from the point of view
 of the users (and the configure script) it is an output file from the point of
 view of the developers (and the autoconf script).
 instance, edit config.h.in.  Though it is an input file from the point of view
 of the users (and the configure script) it is an output file from the point of
 view of the developers (and the autoconf script).