From be55511dfd501993be795477ecee4c542baf9c3e Mon Sep 17 00:00:00 2001
From: Stephan Bergmann <sbergman@redhat.com>
Date: Fri, 26 Oct 2012 11:19:37 +0200
Subject: Turn SAL_INFO back to SAL_WARN

...the reason it started firing was a regression that has now been addressed
with 402eaced7554aaeea75c10015857ea197191ba34 "Related fdo#46808: Fix
UUIInteractionHandler::initialize argument handling."

Change-Id: I2f36e1cb5ae1af293a7c07c366f1602e56e966ea
---
 comphelper/source/misc/namedvaluecollection.cxx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'comphelper')

diff --git a/comphelper/source/misc/namedvaluecollection.cxx b/comphelper/source/misc/namedvaluecollection.cxx
index 70f0796bb429..deb02046ec32 100644
--- a/comphelper/source/misc/namedvaluecollection.cxx
+++ b/comphelper/source/misc/namedvaluecollection.cxx
@@ -217,7 +217,7 @@ namespace comphelper
             else
             {
                 // Once this is rare, this could be turned into a warning.
-                SAL_INFO_IF(
+                SAL_WARN_IF(
                     pArgument->hasValue(), "comphelper",
                     ("NamedValueCollection::impl_assign: encountered a value"
                      " type which I cannot handle: "
-- 
cgit