From b2ae2f6b0e2d06665e9ac63441a80ae13a81967b Mon Sep 17 00:00:00 2001 From: Alexandre Duret-Lutz Date: Sun, 14 Mar 2004 07:26:43 +0000 Subject: [PATCH] * automake.in (handle_texinfo_helper): Typos in comment. --- ChangeLog | 4 ++++ automake.in | 6 +++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 25dec0d..551783f 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2004-03-14 Alexandre Duret-Lutz + + * automake.in (handle_texinfo_helper): Typos in comment. + 2004-03-07 Alexandre Duret-Lutz * lib/config.guess: New upstream version. diff --git a/automake.in b/automake.in index c7f59c3..b27d3b1 100755 --- a/automake.in +++ b/automake.in @@ -2937,11 +2937,11 @@ sub handle_texinfo_helper ($) # because `make dist' always pick files in the build tree # first. # However it turned out the be a bad idea for several reasons: - # * Tru64, OpenBSD, and FreeBSD (not NetBSD) Make do behave + # * Tru64, OpenBSD, and FreeBSD (not NetBSD) Make do not behave # like GNU Make on point (1) above. These implementations # of Make would always rebuild .info files in the build # tree, even if such files were up to date in the source - # tree. Consequently, it was impossible the perform a VPATH + # tree. Consequently, it was impossible to perform a VPATH # build of a package containing Texinfo files using these # Make implementations. # (Refer to the Autoconf Manual, section "Limitation of @@ -2954,7 +2954,7 @@ sub handle_texinfo_helper ($) # build tree can be annoying during development because # - if the files is kept under CVS, you really want it # to be updated in the source tree - # - it os confusing that `make distclean' does not erase + # - it is confusing that `make distclean' does not erase # all files in the build tree. # # Consequently, starting with Automake 1.8, .info files are -- 2.7.4