[SCM] GNU Autoconf source repository branch, master, updated. v2.63b-31-gee4a036

[Ralf Wildenhues]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Autoconf source repository".

http://git.sv.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=ee4a036cda1d3500da82e5410ca12ce38d6c28dc

The branch, master has been updated
       via  ee4a036cda1d3500da82e5410ca12ce38d6c28dc (commit)
      from  c474ab908444e2d6703bd22e4122e551fcdaa96b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit ee4a036cda1d3500da82e5410ca12ce38d6c28dc
Author: Ralf Wildenhues <address@hidden>
Date:   Tue Apr 21 21:43:36 2009 +0200

    manual: fix trivial grammar errors.
    
    * doc/autoconf.texi (Fortran Compiler, Initialization Macros)
    (Limitations of Usual Tools, Pretty Help Strings)
    (config.status Invocation): Fix `a' vs. `an' errors.
    Report by Eric Blake.
    
    Signed-off-by: Ralf Wildenhues <address@hidden>

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog         |    8 ++++++++
 doc/autoconf.texi |   10 +++++-----
 2 files changed, 13 insertions(+), 5 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 943a6cf..05fe4e9 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2009-04-21  Ralf Wildenhues  <address@hidden>
+
+       manual: fix trivial grammar errors.
+       * doc/autoconf.texi (Fortran Compiler, Initialization Macros)
+       (Limitations of Usual Tools, Pretty Help Strings)
+       (config.status Invocation): Fix `a' vs. `an' errors.
+       Report by Eric Blake.
+
 2009-04-21  Eric Blake  <address@hidden>
 
        Shuffle maintainer-specific rules.
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index e6fd489..2d6fd30 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -7553,7 +7553,7 @@ extension and these flags are then used for all 
subsequent @code{FC} tests
 (until @code{AC_FC_SRCEXT} is called again).
 
 For example, you would use @code{AC_FC_SRCEXT(f90)} to employ the
address@hidden extension in future tests, and it would set a
address@hidden extension in future tests, and it would set an
 @code{FCFLAGS_f90} output variable with any extra flags that are needed
 to compile such files.
 
@@ -12811,7 +12811,7 @@ emitting code to open a log within the child.  On the 
other hand, if the
 parent script has @code{AS_MESSAGE_FD} redirected somewhere besides
 @samp{1}, then the child script already has code that copies stdout to
 that descriptor.  Currently, the suggested
-idiom for writing a M4sh shell script from within another script is:
+idiom for writing an M4sh shell script from within another script is:
 
 @example
 AS_INIT_GENERATED(address@hidden, [[# My child script.
@@ -17214,7 +17214,7 @@ should not contain comments.  @acronym{HP-UX} sed has a 
limit of 99 commands
 (not counting @samp{:} commands) and
 48 labels, which can not be circumvented by using more than one script
 file.  It can execute up to 19 reads with the @samp{r} command per cycle.
-Solaris @command{/usr/ucb/sed} rejects usages that exceed an limit of
+Solaris @command{/usr/ucb/sed} rejects usages that exceed a limit of
 about 6000 bytes for the internal representation of commands.
 
 Avoid redundant @samp{;}, as some @command{sed} implementations, such as
@@ -19642,7 +19642,7 @@ strings} do.  This is the purpose of the 
@code{AS_HELP_STRING} macro.
   @dvar{indent-column, 26}, @dvar{wrap-column, 79})
 @asindex{HELP_STRING}
 
-Expands into an help string that looks pretty when the user executes
+Expands into a help string that looks pretty when the user executes
 @samp{configure --help}.  It is typically used in @code{AC_ARG_WITH}
 (@pxref{External Software}) or @code{AC_ARG_ENABLE} (@pxref{Package
 Options}).  The following example makes this clearer.
@@ -20053,7 +20053,7 @@ Synopsis:
 
 It configures each @var{tag}; if none are specified, all the templates
 are instantiated.  A @var{tag} refers to a file or other tag associated
-with a configuration action, as specified by a @code{AC_CONFIG_FOOS}
+with a configuration action, as specified by an @code{AC_CONFIG_FOOS}
 macro (@pxref{Configuration Actions}).  The files must be specified
 without their dependencies, as in
 


hooks/post-receive
--
GNU Autoconf source repository