Update documentation and version output

* libtoolize.in: Overwrite function in bootstrap for printing version
  information for libtoolize.
* build-aux/ltmain.in: Overwrite function in bootstrap for printing
  version information for libtool.
* doc/libtool.texi: Fix typo and correct references for tests/demo
  subdirectory to the tests/demo.at Autotest file.
* gl/top/README-release.diff: Add documentation for maintainers so
  the CVS repository is properly updated following a stable release.

build-aux/ltmain.in

@@ -67,6 +67,29 @@ package_revision=@package_revision@
 # Set a version string.
 scriptversion='(GNU @PACKAGE@) @VERSION@'
 
+# func_version
+# ------------
+# Echo version message to standard output and exit.
+func_version ()
+{
+    $debug_cmd
+
+	year=`date +%Y`
+
+	cat <<EOF
+$progname $scriptversion
+Copyright (C) $year Free Software Foundation, Inc.
+License GPLv2+: GNU GPL version 2 or later <https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.
+
+Originally written by Gordon Matzigkeit, 1996
+(See AUTHORS for complete contributor listing)
+EOF
+
+    exit $?
+}
+
 
 # func_echo ARG...
 # ----------------

doc/libtool.texi

@@ -1279,7 +1279,7 @@ Do not print out any progress or informational messages.
 @item -v
 @itemx --verbose
 Print out progress and informational messages (enabled by default),
-as well as additional messages not ordinary seen by default.
+as well as additional messages not ordinarily seen by default.
 
 @item --no-quiet
 @itemx --no-silent
@@ -1991,9 +1991,11 @@ mirror, install it, and start using it.
 Learn how to write @file{Makefile} rules by hand.  They're sometimes complex,
 but if you're clever enough to write rules for compiling your old
 libraries, then you should be able to figure out new rules for libtool
-libraries (hint: examine the @file{Makefile.in} in the @file{tests/demo}
-subdirectory of the libtool distribution@dots{} note especially that it
-was automatically generated from the @file{Makefile.am} by Automake).
+libraries (hint: examine the @file{Makefile.in} in the
+@file{tests/testsuite.dir/027} subdirectory, generated from the Autotest
+labeled 'link against a preloaded static library' in @file{tests/demo.at},
+of the libtool distribution; note especially that it was automatically
+generated from the @file{Makefile.am} by Automake).
 @end enumerate
 
 @node Using Automake
@@ -2004,7 +2006,7 @@ Libtool library support is implemented under the @samp{LTLIBRARIES}
 primary.
 
 Here are some samples from the Automake @file{Makefile.am} in the
-libtool distribution's @file{demo} subdirectory.
+libtool distribution's @file{tests/demo.at}.
 
 First, to link a program against a libtool library, just use the
 @samp{program_LDADD}@footnote{@c
@@ -3298,12 +3300,32 @@ Non-ANSI compilers will report errors if functions are prototyped.
 These complications mean that your library interface headers must use
 some C preprocessor magic to be usable by each of the above compilers.
 
-@file{foo.h} in the @file{tests/demo} subdirectory of the libtool
-distribution serves as an example for how to write a header file that
+@file{foo.h}, defined in the @file{tests/demo.at} Autotest of the libtool
+distribution, serves as an example for how to write a header file that
 can be safely installed in a system directory.
 
 Here are the relevant portions of that file:
 
+@example
+#ifndef FOO_H
+#define FOO_H
+
+#ifdef __cplusplus
+extern "C" @{
+#endif
+
+int foo (void);
+int hello (void);
+
+#ifdef __cplusplus
+@}
+#endif
+
+#endif /* !FOO_H */
+@end example
+
+This can also be achieved by utilizing macros:
+
 @example
 /* BEGIN_C_DECLS should be used at the beginning of your declarations,
    so that C++ compilers don't mangle their names.  Use END_C_DECLS at
@@ -3331,11 +3353,11 @@ Here are the relevant portions of that file:
 #endif
 @end example
 
-These macros are used in @file{foo.h} as follows:
+These macros can be used in @file{foo.h} as follows:
 
 @example
 #ifndef FOO_H
-#define FOO_H 1
+#define FOO_H
 
 /* The above macro definitions. */
 #include "@dots{}"

gl/top/README-release.diff

@@ -36,3 +36,16 @@
  
  * To (i) set the date, version number, and release TYPE on line 3 of
    NEWS, (ii) commit that, and (iii) tag the release, run
+@@ -98,4 +115,12 @@
+ 
+   to update the on-line manual accessible at
+ 
+     https://www.gnu.org/software/@PACKAGE@/manual/
++
++  Ensure that the on-line documentation links to the latest stable release:
++
++     https://www.gnu.org/software/@PACKAGE@/
++
++  On-line documentation is updated through the CVS repository:
++
++    https://savannah.gnu.org/cvs/?group=@PACKAGE@

libtoolize.in

@@ -63,6 +63,27 @@
 # Set a version string.
 scriptversion='(GNU @PACKAGE@) @VERSION@'
 
+# func_version
+# ------------
+# Echo version message to standard output and exit.
+func_version ()
+{
+    $debug_cmd
+
+	year=`date +%Y`
+
+	cat <<EOF
+$progname $scriptversion
+Copyright (C) $year Free Software Foundation, Inc.
+License GPLv2+: GNU GPL version 2 or later <https://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.
+
+Written by Gary V. Vaughan <gary@gnu.org>, 2003
+EOF
+
+    exit $?
+}
 
 ## ---------------- ##
 ## Options parsing. ##