Fix minor doc issues in node `CVS'.

* doc/automake.texi (CVS): configure.ac will appear newer, not
older, than configure.  Use `lexical' instead of `alphabetical'.

diff --git a/ChangeLog b/ChangeLog
index a124ae0cd5f8cfffef4eab9dd11156f83522993d..683e02ed57118b0b5639f6b47cc1e87654d0e732 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2008-02-05  Reuben Thomas  <rrt@sc3d.org>
+
+       * doc/automake.texi (CVS): configure.ac will appear newer, not
+       older, than configure.  Use `lexical' instead of `alphabetical'.
+
 2008-01-30  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
 
        * tests/man3.test: Avoid `make VAR=value'.

diff --git a/doc/automake.texi b/doc/automake.texi
index 9d311bec2512a63f55d66a69462def3b292371a3..c0ace407e68d27e541249c3533db76841e3e34df 100644 (file)
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -9636,8 +9636,8 @@ update, not the original timestamp of this revision.  This is meant to
 make sure that @command{make} notices sources files have been updated.
 
 This timestamp shift is troublesome when both sources and generated
-files are kept under CVS@.  Because CVS processes files in alphabetical
-order, @file{configure.ac} will appear older than @file{configure}
+files are kept under CVS@.  Because CVS processes files in lexical
+order, @file{configure.ac} will appear newer than @file{configure}
 after a @command{cvs update} that updates both files, even if
 @file{configure} was newer than @file{configure.ac} when it was
 checked in.  Calling @command{make} will then trigger a spurious rebuild