Renamed configure.in to the more modern name configure.ac

[mmh] / docs / README.developers

diff --git a/docs/README.developers b/docs/README.developers
index 23a1d2d..31a6e46 100644 (file)
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -1,8 +1,6 @@
 #
 # README.developers
 #
-# $Id$
-#
 
 This file is intended to provide a few tips for anyone doing development on nmh.
 Developers who learn things "the hard way" about the nmh codebase (as opposed to
@@ -21,14 +19,14 @@ GNU autoconf (<ftp://ftp.gnu.org/pub/gnu/autoconf/>).  Nmh is currently using
 a minimum of autoconf 2.54.
 
 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 acconfig.h and configure.ac.  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).
 
 Note that the automatically generated autoconf files (such as config.h.in,
-stamp-h.in, and configure), are NOT kept in CVS.  Thus, when you check out
-a CVS tree, you need to run the autogen.sh script before you can build
+stamp-h.in, and configure), are NOT kept in git.  Thus, when you check out
+a git tree, you need to run the autogen.sh script before you can build
 anything:
 
        % ./autogen.sh
@@ -121,6 +119,18 @@ zotnet/tws/ (deprecated, now in sbr/)
     away completely.
 
 
+---
+git
+---
+
+As of December 2010, nmh has switched to using git for revision control
+instead of CVS.  While the topic of git is beyond the scope of this FAQ,
+to get started with git & nmh, you can run the following command to checkout
+the nmh repository:
+
+    % git clone git://git.savannah.nongnu.org/nmh.git
+
+
 -------------------------------------------------------
 nmh-local functions to use in preference to OS versions
 -------------------------------------------------------