Lubomir Rintel 57a26fd2aa cli/connections: decide about activation success and failure in single place ... Track both device and active connections at the same time and decide whether activation finished (either successfully or not) in a single place, check_activated(). This makes the already too complex code path a bit more straightforward and also makes it possible to be more reasonable about the diagnostics. Now that the active connection signals the reason, we include it; but if the failure is due to the device disconnection while we're activating, include a device reason instead, since it's often more useful. Like: Before: Error: Connection activation failed. Without considering the device: Error: Connection activation failed: the base network connection was interrupted After: Error: Connection activation failed: The Wi-Fi network could not be found		2017-03-17 10:21:19 +01:00
..
cli	cli/connections: decide about activation success and failure in single place	2017-03-17 10:21:19 +01:00
common	include: use double-quotes to include our own headers	2017-03-09 14:12:35 +01:00
tui	all: use "unsigned" instead of "unsigned int"	2017-03-14 11:26:29 +01:00
nm-online.c	nm-online: fix wrong assertion failure during nm-online	2017-02-07 19:42:30 +01:00