From 553f80295ae2959ad63871e0ce578147a6fb22a3 Mon Sep 17 00:00:00 2001 From: Reuben Thomas Date: Tue, 5 Feb 2008 21:02:45 +0100 Subject: [PATCH] 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'. --- ChangeLog | 5 +++++ doc/automake.texi | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index a124ae0cd..683e02ed5 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2008-02-05 Reuben Thomas + + * doc/automake.texi (CVS): configure.ac will appear newer, not + older, than configure. Use `lexical' instead of `alphabetical'. + 2008-01-30 Ralf Wildenhues * tests/man3.test: Avoid `make VAR=value'. diff --git a/doc/automake.texi b/doc/automake.texi index 9d311bec2..c0ace407e 100644 --- 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 -- 2.34.1