-The reason for the three-step commit is that configure.in contains the RCS $Id
-keyword, so when you commit it, a new version is written locally. Therefore,
-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.
+Note that the automatically generated autotools files (such as config.h.in,
+Makefile.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: