Update NEWS about the warnings-over-strictness precedence.

* NEWS: Automake explicit warning levels always take precedence
over the implicit warning levels implied by Automake strictness.

diff --git a/ChangeLog b/ChangeLog
index 050ec979a0ac4c3ff7245c0dd9af9a3ee9dfe626..b5eb29852382250fde9678d71608ee829ff07831 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2011-01-15  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
+       Update NEWS about the warnings-over-strictness precedence.
+       * NEWS: Automake explicit warning levels always take precedence
+       over the implicit warning levels implied by Automake strictness.
+
        For PR automake/547:
        Warnings win over strictness in AUTOMAKE_OPTIONS.
        Ensure that, for what concerns the options specified in

diff --git a/NEWS b/NEWS
index 417cc5cfc9e3206b1a7ac4482b4591631b086e90..bbc177d76cdb1b86f3f9fe0099a94cc5895c4b34 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -108,6 +108,15 @@ Bugs fixed in 1.11a:
 
   - Automake now complains if a `*YFLAGS' variable has any conditional
     content, not only a conditional definition.
+
+  - Explicit enabling and/or disabling of Automake warning categories
+    through the `-W...' options now always takes precedence over the
+    implicit warning level implied by Automake strictness (foreign, gnu
+    or gnits),  regardless of the order in which such strictness and
+    warning flags appear.  For example, a setting like:
+      AUTOMAKE_OPTIONS = -Wall --foreign
+    will cause the warnings in category `portability' to be enabled, even
+    if those warnings are by default disabled in `foreign' strictness.
 \f
 New in 1.11: