This is [PATCH 11/10] of the older series, which has already been reviewed
and ACK'd "with nits addressed", so a new review shouldn't be required.
Anyway, the amended patch is attached, for completeness.

Regards,
   Stefano


From 2f6a606fea2c06de56fd208f18ff8c72838465ff Mon Sep 17 00:00:00 2001
From: Stefano Lattarini <stefano.lattar...@gmail.com>
Date: Fri, 24 Dec 2010 18:52:05 +0100
Subject: [PATCH 8/9] 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.
---
 ChangeLog |    6 ++++++
 NEWS      |    9 +++++++++
 2 files changed, 15 insertions(+), 0 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index fa2cfd3..11c128f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,11 @@
 2011-01-02  Stefano Lattarini  <stefano.lattar...@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.
+
+2011-01-02  Stefano Lattarini  <stefano.lattar...@gmail.com>
+
 	For PR automake/547:
 	Warnings win over strictness in AUTOMAKE_OPTIONS.
 	This change ensures that, for what concerns the options specified
diff --git a/NEWS b/NEWS
index a7c5914..5d98224 100644
--- a/NEWS
+++ b/NEWS
@@ -96,6 +96,15 @@ Bugs fixed in 1.11a:
   - The code for automatic dependency tracking works around a Solaris
     make bug triggered by sources containing repeated slashes when the
     `subdir-objects' was used.
+
+  - 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.
 
 New in 1.11:
 
-- 
1.7.2.3

Reply via email to