X-Git-Url: http://git.marmaro.de/?a=blobdiff_plain;f=docs%2FREADME.developers;h=522244a1fc5ef45d4714834ad0d921182821b8dc;hb=fc80e34e8e9e3c726073d321e2075ead77baba08;hp=b243b5d3754f49042085785704f5ccad2555ad76;hpb=d3df81fcf2e52e4e484da1c1df431c7a915a3139;p=mmh

diff --git a/docs/README.developers b/docs/README.developers
index b243b5d..522244a 100644
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -44,17 +44,21 @@ around with `touch'.
 The correct procedure to commit the configure-related files is:
 
     % cvs commit acconfig.h aclocal.m4 configure.in
-    % autoconf && autoheader
+    % autoconf && autoheader                          # or simply "make"
     % cvs commit config.h.in configure
-    % make stamp-h.in
+    % make stamp-h.in                                 # or simply "make"
     % 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).  The reason for
-the sequence is the RCS Id strings in the edited files -- they change when
-you commit the changes.
+The reason that the commits need to be split up is that the timestamps on the
+files change when the commits are done and the RCS Ids change.  If one committed
+all the files in one fell swoop (in the above relative order), timestamps would
+cause unnecessary autoconf regeneration on 'make's after the commit, which would
+waste your time and would cause your local stamp-h.in to be out-of-sync with the
+one checked into CVS (not the end of the world, but...).
 
-You can run just "make" instead of the other commands in between cvs commits.
+If you haven't changed all the files noted above, just commit the ones you have,
+in the stated order (for instance, configure.in, then configure, then
+stamp-h.in).
 
 
 -------------------