Thomas Haller a63867a40b build: use NetworkManager logging domain for device and settings plugins ... First of all, G_LOG_DOMAIN only matters when using g_log() directly. Inside core, we always want to log via nm-logging. Every call to a g_log() is a bug in the first place (like a failed assertion that logs a g_critical() during g_return_if_fail()). So, for all practic purposes, the logging domain is not used. For nm-logging, the G_LOG_DOMAIN has no effect. Unless we find a proper use of this domain, G_LOG_DOMAIN should not differ from what the rest of core.		2016-10-06 20:41:20 +02:00
..
tests	build: use NetworkManager logging domain for device and settings plugins	2016-10-06 20:41:20 +02:00
Makefile.am	build: use NetworkManager logging domain for device and settings plugins	2016-10-06 20:41:20 +02:00
nm-ibft-connection.c	core: refactor private data in "src"	2016-10-04 09:50:56 +02:00
nm-ibft-connection.h	core: refactor private data in "src"	2016-10-04 09:50:56 +02:00
plugin.c	core: refactor private data in "src"	2016-10-04 09:50:56 +02:00
plugin.h	core: refactor private data in "src"	2016-10-04 09:50:56 +02:00
reader.c	all: cleanup includes and let "nm-default.h" include "config.h"	2016-02-19 17:53:25 +01:00
reader.h	all: cleanup includes in header files	2016-08-17 19:51:17 +02:00