Thomas Haller 29bcfc2522 cli: don't track output data in global NmCli structure ... We should not violate the global data to track the output data while it is constructed and printed. Most of the time, we actually clear the output data anyway -- either before constructing it, or after printing it. In some cases we didn't, but I think that is a bug. It's really hard to keep track of this. The output data should belong to a certain scope and get destroyed afterwards. Passing it around is very confusing. Don't do that.		2017-03-30 14:56:21 +02:00
..
cli	cli: don't track output data in global NmCli structure	2017-03-30 14:56:21 +02:00
common	cli: use enum property type for connection.lldp	2017-03-30 13:09:58 +02: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