X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=docs%2FREADME.developers;h=0fe6311212951056821c2256524665acf27f8715;hp=f93c70bd72a4afe7eb969031bc02ea68eee0b90a;hb=cc9976fbd511140bf7eef525a447c6e47f17850e;hpb=2ef1a2bc54aa523b9edbb830959f17a3ed05d74d

diff --git a/docs/README.developers b/docs/README.developers
index f93c70b..0fe6311 100644
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -51,9 +51,14 @@ The correct procedure to commit the configure-related files is:
 
 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>]  If this were
-not the case, you could commit with a single make followed by a
+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>]
 
 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