Merge branch 'maint'

* maint:
  NEWS: one more minor fixlet
  maint: port check-minimal-autoconf to VPATH builds
  tests: avoid spurious failures in Linux -> MinGW cross-compilation mode
  tests: simplify checks for some expected variables values in Makefiles
  NEWS: improve and update wording
  tests: fix/improve few heading comments
  coverage: new test on Texinfo @include support
  tests: tighten a grepping check
  tests: more significant names for some tests
  rename-tests: rework some code for clarity and safety
  tests: cosmetic changes in t/extra-sources.sh
  rename-tests: inform the user about the pre-filled commit msg
  typofix: in comments in 'maintainer/rename-tests'
  rename-tests: also "git add" list-of-tests.mk
  tests: rename t/exsource.sh -> t/extra-sources.sh

Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>

diff --cc NEWS
index 400372c2cb8790a10ead50c6e595de5965edf0ca,39ad7a36510a6f47f1c0cd808fd74db587f4f332..56ae09cb342df1c29b9a187be576de3af9984197
--- 1/NEWS
--- 2/NEWS
+++ b/NEWS
@@@ -1,71 -1,13 +1,71 @@@
 +New in 2.0:
 +
 +* Compilation and object files:
 +
 + - If a source file is placed in a subdirectory, the corresponding compiled
 +   object will *always* be put into the subdirectory named after the source
 +   file, rather than in the current directory.  For instance, 'src/file.c'
 +   and 'src/file.f90' will be compiled to 'src/file.o', and 'sub/dir/mu.cc'
 +   will be compiled to 'sub/dir/mu.o'.  Put in another way, Automake 2.0
 +   and later will *unconditionally* behave as older Automake versions did
 +   when the 'subdir-objects' option was given.
 +
 +* Aclocal search path:
 +
 +  - Third-party m4 files located in the system-wide aclocal directory,
 +    as well as in any directory listed in the ACLOCAL_PATH environment
 +    variable, now take precedence over "built-in" Automake macros.
 +    For example, assuming Automake is installed in the '/usr/local'
 +    hierarchy, a definition of the AM_PROG_VALAC macro found in file
 +    (say) '/usr/local/share/aclocal/my-vala.m4' should take precedence
 +    over the same-named automake-provided macro, as defined in file
 +    '/usr/local/share/aclocal-2.0/vala.m4'.
 +
 +* Obsolescent features flagged:
 +
 +  - Use of the special makefile variable 'ACLOCAL_AMFLAGS' is deprecated.
 +    To specify locations of extra m4 files, the 'AC_CONFIG_MACRO_DIR' or
 +    'AC_CONFIG_MACRO_DIRS' (the latter introduced with autoconf 2.70)
 +    should be used instead.  And use of the '--install' aclocal option in
 +    'ACLOCAL_AMFLAGS' has proved to be a bad idea anyway -- see automake
 +    bug#9037.
 +
 +* Obsolete features removed:
 +
 +  - Support for the long-deprecated name 'configure.in' for the Autoconf
 +    input file has been removed altogether.  Just use the modern name
 +    'configure.ac' instead.
 +
 +  - Support for the long-obsolete variable $(ACLOCAL_M4_SOURCES) has
 +    been removed.  It should be safe to simply remove any definition
 +    of it you have in your Makefiles.
 +
 +* Removed support for obsolete platforms:
 +
 +  - Support for automatic dependency tracking with the SGI C/C++ compilers
 +    on IRIX has been removed.  The SGI depmode had been reported broken
 +    "in the wild" already, and we don't think investing time in debugging
 +    and fixing it would have been worthwhile, especially considering that
 +    SGI has last updated those compilers in 2006, and is expected to retire
 +    support for them in December 2013:
 +    <http://www.sgi.com/services/support/irix_mips_support.html>
 +
 +  - Support for DJGPP on MS-DOS and/or Windows 95/98/ME has been removed.
 +    Note that both Cygwin and MSYS/MinGW on modern Windows versions will
 +    continue to be fully supported.
 +
 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +
  * WARNING: New versioning scheme for Automake.
  
-   - Starting with this version onward, Automake will use an update and
-     more rational versioning scheme, one that will allow users to know
-     which kind of changes can be expected from a new version, based on
-     its version number.
- 
-     + Micro versions (e.g., 1.13.3, 2.0.1, 3.2.8) will introduce only
-       documentation updates and bug and regression fixes; they will
-       not introduce new features, nor any backward-incompatibility (any
+   - Beginning with the release 1.13.2, Automake has started to use a
+     more rational versioning scheme, that should allow users to know
+     which kind of changes can be expected from a new version, based
+     on its version number.
+ 
+     + Micro releases (e.g., 1.13.3, 2.0.1, 3.2.8) introduce only bug
+       and regression fixes and documentation updates; they should not
+       introduce new features, nor any backward-incompatibility (any
        such incompatibility would be considered a bug, to be fixed with
        a further micro release).
  

diff --cc t/list-of-tests.mk
Simple merge