One more pass at README.developers now that it's clear that my

previously-suggested one-line autoconf-file commit can cause unnecessary local
makes and an out-of-sync stamp-h.in file, but would not cause problems for other
people using the CVS files.

diff --git a/ChangeLog b/ChangeLog
index f4e32df..d0485a6 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -3,10 +3,14 @@ Mon Jul 17 13:11:52 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
        * Moved Kimmo's new "--with-hash-backup" to be output with the
        rest of the --with options in the configure --help output.
 
        * Moved Kimmo's new "--with-hash-backup" to be output with the
        rest of the --with options in the configure --help output.
 

+       * One more pass at README.developers now that it's clear that my
+       previously-suggested one-line autoconf-file commit can cause
+       unnecessary local makes and an out-of-sync stamp-h.in file, but
+       would not cause problems for other people using the CVS files.
+

 Tue Jul 18 19:36:59 EDT 2000 Kimmo Suominen <kim@tac.nyc.ny.us>
 
 Tue Jul 18 19:36:59 EDT 2000 Kimmo Suominen <kim@tac.nyc.ny.us>
 

-       * Added the obvious answer to Dan's question in README.developers;
-       I'm not sure why we don't just have this discussion in e-mail.
+       * Added the answer to Dan's question in README.developers.

 
 Mon Jul 17 19:10:36 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
 
 
 Mon Jul 17 19:10:36 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
 

diff --git a/docs/README.developers b/docs/README.developers
index 0fe6311..522244a 100644 (file)
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -49,16 +49,12 @@ The correct procedure to commit the configure-related files is:
     % make stamp-h.in                                 # or simply "make"
     % cvs commit stamp-h.in
 
     % make stamp-h.in                                 # or simply "make"
     % cvs commit stamp-h.in
 

-The reason that the commits need to be split up is that the RCS Id strings
-in the files change when you commit, which can apparently mess up the
-dependencies.  [How?  -- Dan Harkless <dan-nmh@dilvish.speed.net> // CVS
-updates the strings to have the new version number, the modification time
-of the file gets updated by the OS.  -- Kimmo Suominen <kim@tac.nyc.ny.us>]
-If this were not the case, you could commit with a single make followed by a
-cvs commit acconfig.h aclocal.m4 config.h.in configure.in configure stamp-h.in.
-[But since we have the RCS Id strings in the files, isn't it useless to even
-mention this?  The fix would be to remove the strings, and I don't think that
-would be good.  -- Kimmo Suominen <kim@tac.nyc.ny.us>]
+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...).

 
 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
 
 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