[FYI] {maint} plans: update w.r.t. latest changes

[Stefano Lattarini]

Signed-off-by: Stefano Lattarini <address@hidden>
---
 PLANS/subdir-objects.txt                           | 37 +++++++++++-----------
 .../warnings-for-automake-ng-compatibility.txt     |  4 +--
 2 files changed, 20 insertions(+), 21 deletions(-)

diff --git a/PLANS/subdir-objects.txt b/PLANS/subdir-objects.txt
index e3aec6b..e4e6e25 100644
--- a/PLANS/subdir-objects.txt
+++ b/PLANS/subdir-objects.txt
@@ -24,33 +24,28 @@ Alas, since this also means changing the default behaviour 
of Automake
 ('subdir-objects' is not enabled by default, sadly), this means the
 transition path will be less smooth than I'd like.
 
-For automake 1.13.2 (ASAP)
---------------------------
+DONE for automake 1.13.2
+------------------------
 
-Fix the bug spotted by Nick Bowler:
+The bug spotted by Nick Bowler:
 
   <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
   <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
 
-and exposed in test case 't/ccnoco4.sh': currently, Automake-generated
-C compilation rules mistakenly pass the "-c -o" options combination
-unconditionally (even to losing compiler) when the 'subdir-objects' is
-used but sources are only present in the top-level directory.
+and exposed in test case 't/ccnoco4.sh' has been fixed (see commit
+v1.13.1-56-g34001a9).  The bug was due to the fact that Automake-generated
+C compilation rules mistakenly passed the "-c -o" options combination
+unconditionally (even to losing compiler) when the 'subdir-objects' was
+used but sources were only present in the top-level directory.
 
-For automake 1.13.2 (with more ease)
-------------------------------------
+TODO for automake 1.13.2
+------------------------
 
 Give a warning in the category 'unsupported' if the 'subdir-objects'
 option is not specified.  This should give the users enough forewarning
 about the planned change, and give them time to update their packages
 to the new semantic.
 
-This warning, when there are C sources in subdirs, should also mention the
-need to use AM_PROG_CC_C_O in configure.ac (thanks to Peter Breitenlohner
-for suggesting this).  This is not strictly required, but will make
-things a little simpler for the users, by giving a more complete feedback:
-<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#29>
-
 Be sure to avoid the warning when it would be irrelevant, i.e., if all
 source files sit in "current" directory (thanks to Peter Johansson for
 suggesting this).
@@ -58,10 +53,14 @@ suggesting this).
 For automake 1.14
 -----------------
 
-Flip the 'subdir-object' option on by default.  At the same time,
-drop support for the "old" behaviour of having object files derived
-from sources in a subdirectory being placed in the current directory
-rather than in that same subdirectory.
+Remove the copy & paste of Autoconf internals in our AC_PROG_CC rewrite
+See the first patch in the series:
+<http://lists.gnu.org/archive/html/automake-patches/2013-01/msg00102.html>
+
+Make the behaviour once activated by the 'subdir-object' option mandatory.
+With that change, we'll drop support for the "old" behaviour of having
+object files derived from sources in a subdirectory being placed in the
+current directory rather than in that same subdirectory.
 
 Still keep the 'subdir-object' option supported (as a simple no-op
 now), to save useless churn in our user's build systems.
diff --git a/PLANS/texi/warnings-for-automake-ng-compatibility.txt 
b/PLANS/texi/warnings-for-automake-ng-compatibility.txt
index 1dd3da3..aca46b4 100644
--- a/PLANS/texi/warnings-for-automake-ng-compatibility.txt
+++ b/PLANS/texi/warnings-for-automake-ng-compatibility.txt
@@ -1,5 +1,5 @@
-For automake 1.13.2:
---------------------
+Done in automake 1.13.2:
+------------------------
 
 I have discouraged the use of '.txi' and '.texinfo' suffixes for
 Texinfo inputs (see commit 'v1.13.1-6-ge1ed314') and the generation
-- 
1.8.1.rc3.192.g2d0029e