From: Alexandre Duret-Lutz <adl@gnu.org>
Date: Wed, 26 Jun 2002 08:37:48 +0000 (+0000)
Subject: * automake.texi: s/.../@dots{}/.
X-Git-Tag: Release-1-6b~48
X-Git-Url: https://sourceware.org/git/?a=commitdiff_plain;h=ded1d9cd5e37d5b67dc13c8350f9909143c71c3a;p=automake.git

* automake.texi: s/.../@dots{}/.
---

diff --git a/ChangeLog b/ChangeLog
index c71ccd0b..6cfca8a7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2002-06-26  Art Haas  <ahaas@neosoft.com>
+
+	* automake.texi: s/.../@dots{}/.
+
 2002-06-26  Alexandre Duret-Lutz  <duret_g@epita.fr>
 
 	* configure.in: Check that ln works, fall back to `cp -p'.
diff --git a/THANKS b/THANKS
index a4087a22..83a70194 100644
--- a/THANKS
+++ b/THANKS
@@ -18,6 +18,7 @@ Andris Pavenis		pavenis@lanet.lv
 Angus Leeming		a.leeming@ic.ac.uk
 Anthony Green		green@cygnus.com
 Arkadiusz Miskiewicz	misiek@pld.ORG.PL
+Art Haas		ahaas@neosoft.com
 Assar Westerlund	assar@sics.se
 Axel Belinfante		Axel.Belinfante@cs.utwente.nl
 Bernard Urban		Bernard.Urban@meteo.fr
diff --git a/automake.texi b/automake.texi
index 3104a8be..cc822093 100644
--- a/automake.texi
+++ b/automake.texi
@@ -636,7 +636,7 @@ commands that @code{automake} needs.  The way to do this is to add an
 @example
 AC_INIT(zardoz, 1.0)
 AM_INIT_AUTOMAKE
-...
+@dots{}
 @end example
 
 Since your program doesn't have any complicating factors (e.g., it
@@ -650,7 +650,7 @@ you're done with this part.  That was easy!
 Now you must regenerate @file{configure}.  But to do that, you'll need
 to tell @code{autoconf} how to find the new macro you've used.  The
 easiest way to do this is to use the @code{aclocal} program to generate
-your @file{aclocal.m4} for you.  But wait... maybe you already have an
+your @file{aclocal.m4} for you.  But wait@dots{} maybe you already have an
 @file{aclocal.m4}, because you had to write some hairy macros for your
 program.  The @code{aclocal} program lets you put your own macros into
 @file{acinclude.m4}, so simply rename and then run:
@@ -1975,13 +1975,13 @@ You can then setup the @code{@@HELLO_SYSTEM@@} substitution from
 @file{configure.in}:
 
 @example
-...
+@dots{}
 case $host in
   *linux*) HELLO_SYSTEM='hello-linux.$(OBJEXT)' ;;
   *)       HELLO_SYSTEM='hello-generic.$(OBJEXT)' ;;
 esac
 AC_SUBST([HELLO_SYSTEM])
-...
+@dots{}
 @end example
 
 In this case, @code{HELLO_SYSTEM} should be replaced by
@@ -2312,7 +2312,7 @@ So for instance, if you want the hypothetical @file{maude} compilations
 to also use the value of @samp{AM_CFLAGS}, you would need to write:
 
 @example
-maude_CFLAGS = ... your flags ... $(AM_CFLAGS)
+maude_CFLAGS = @dots{} your flags @dots{} $(AM_CFLAGS)
 @end example
 
 @item maude_DEPENDENCIES
@@ -4744,7 +4744,7 @@ Automake's programing interface is not easy to define.  Basically it
 should include at least all @strong{documented} variables and targets
 that a @samp{Makefile.am} authors can use, the behaviours associated to
 them (e.g. the places where @samp{-hook}'s are run), the command line
-interface of @samp{automake} and @samp{aclocal}, ...
+interface of @samp{automake} and @samp{aclocal}, @dots{}
 
 @heading What is not in the API
 
diff --git a/stamp-vti b/stamp-vti
index f608a27d..e62037e3 100644
--- a/stamp-vti
+++ b/stamp-vti
@@ -1,4 +1,4 @@
-@set UPDATED 17 June 2002
+@set UPDATED 26 June 2002
 @set UPDATED-MONTH June 2002
 @set EDITION 1.6a
 @set VERSION 1.6a
diff --git a/version.texi b/version.texi
index f608a27d..e62037e3 100644
--- a/version.texi
+++ b/version.texi
@@ -1,4 +1,4 @@
-@set UPDATED 17 June 2002
+@set UPDATED 26 June 2002
 @set UPDATED-MONTH June 2002
 @set EDITION 1.6a
 @set VERSION 1.6a