summaryrefslogtreecommitdiff
path: root/libnm-util
diff options
context:
space:
mode:
authorDan Winship <danw@gnome.org>2014-08-08 12:15:10 -0400
committerDan Winship <danw@gnome.org>2014-08-08 12:15:10 -0400
commitb64c82a3ed75c15104f3dd5d43fa07ff60b6151c (patch)
tree103d6c560281b0b31d1d37c11c48f84b8d8e656f /libnm-util
parent58a66cc70ba73cf1a0fce1583277962a38eef2dd (diff)
downloadNetworkManager-b64c82a3ed75c15104f3dd5d43fa07ff60b6151c.tar.gz
libnm-util: don't warn about unrecognized properties
libnm-util is expected to end up behind the curve in terms of knowing about new NMSetting properties, so if it sees an unknown property, it should just assume that there will also be a backward-compatibility equivalent rather than printing a warning. (In particular, it should not warn when it sees the "ipv4.address-labels" property now that it now longer knows about it.)
Diffstat (limited to 'libnm-util')
-rw-r--r--libnm-util/nm-setting.c6
1 files changed, 4 insertions, 2 deletions
diff --git a/libnm-util/nm-setting.c b/libnm-util/nm-setting.c
index 94a0cac6e9..b479bf4aa0 100644
--- a/libnm-util/nm-setting.c
+++ b/libnm-util/nm-setting.c
@@ -394,8 +394,10 @@ nm_setting_new_from_hash (GType setting_type, GHashTable *hash)
param_spec = g_object_class_find_property (class, prop_name);
if (!param_spec) {
- /* Oh, we're so nice and only warn, maybe it should be a fatal error? */
- g_warning ("Ignoring invalid property '%s'", prop_name);
+ /* Assume that any unrecognized property either can be ignored, or
+ * else has a backward-compatibility equivalent.
+ */
+ g_debug ("Ignoring unrecognized property '%s'", prop_name);
continue;
}