automake-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where's the sequel?!


From: Ralf Wildenhues
Subject: Re: Where's the sequel?!
Date: Sun, 22 Jul 2007 11:28:12 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

Hello Reuben,

* Reuben Thomas wrote on Fri, Jul 20, 2007 at 09:26:44PM CEST:
> 
> "For this reason we refer to such setups using the name _VPATH builds_ in 
> the sequel."
> 
> I am presuming you mean "we refer below to such setups as _VPATH builds_." 
> rather than what you wrote, exciting as it sounds.

Thanks for proof-reading the manual!  Having a native speaker aboard is
always good! ;-)

I've applied this to branch-1-10 and HEAD.

Cheers,
Ralf

        * doc/automake.texi (VPATH Builds): Fix wording.
        Report by Reuben Thomas.

Index: doc/automake.texi
===================================================================
RCS file: /cvs/automake/automake/doc/automake.texi,v
retrieving revision 1.169
diff -u -r1.169 automake.texi
--- doc/automake.texi   16 Jul 2007 21:55:43 -0000      1.169
+++ doc/automake.texi   22 Jul 2007 09:24:58 -0000
@@ -819,7 +819,7 @@
 reference to the way the build tree shadows the source tree, it is not
 about some concurrency in the way build commands are run.  For this
 reason we refer to such setups using the name @emph{VPATH builds} in
-the sequel.  @emph{VPATH} is the name of the @command{make} feature
+the following.  @emph{VPATH} is the name of the @command{make} feature
 used by the @file{Makefile}s to allow these builds (@pxref{General
 Search, , @code{VPATH}: Search Path for All Prerequisites, make, The
 GNU Make Manual}).




reply via email to

[Prev in Thread] Current Thread [Next in Thread]