Whoops, user & port were in the wrong order so msgchk didn't work for POP

[mmh] / docs / README.developers

diff --git a/docs/README.developers b/docs/README.developers
index a85f37d..f026c74 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
@@ -27,13 +25,11 @@ 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 do the following things 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:
 
-       % autoheader
-       % autoconf
-       % date > stamp-h.in
+       % ./autogen.sh
 
 -------------------
 directory structure
@@ -123,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
 -------------------------------------------------------