+2009-04-19 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
+
+ Improve and clarify `config.status' usage documentation.
+ * doc/autoconf.texi (config.status Invocation): Fix markup in
+ synopsis. Use `tag' instead of `file' notation for the
+ non-option arguments, to be consistent with the documentation
+ of the AC_CONFIG_* macros.
+ * lib/autoconf/status.m4 (_AC_OUTPUT_CONFIG_STATUS): Likewise,
+ use `tag' notation for non-option arguments.
+ Report by John Calcote.
+
2009-04-15 Eric Blake <ebb9@byu.net>
Test that autotest handles binary output.
Synopsis:
@example
-./config.status @var{option}@dots{} [@var{file}@dots{}]
+./config.status @ovar{option}@dots{} @ovar{tag}@dots{}
@end example
-It configures the @var{files}; if none are specified, all the templates
-are instantiated. The files must be specified without their
-dependencies, as in
+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}
+macro (@pxref{Configuration Actions}). The files must be specified
+without their dependencies, as in
@example
./config.status foobar
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
ac_cs_usage="\
-\`$as_me' instantiates files from templates according to the
-current configuration.
+\`$as_me' instantiates files and other configuration actions
+from templates according to the current configuration. Unless the files
+and actions are specified as TAGs, all are instantiated by default.
-Usage: $[0] [[OPTION]]... [[FILE]]...
+Usage: $[0] [[OPTION]]... [[TAG]]...
-h, --help print this help, then exit
-V, --version print version number and configuration settings, then exit