Thomas Haller 649968632e cli: merge remove-property, reset-property and set-property ... It's fundamentally wrong to have separate "remove_fcn" and "set_fcn" implementations. Set, reset, add, and remove are all similar, and should be implemented in a similar manner. Merge the implementations all in set-property, which now can: - reset the value (value == NULL && modifier == '\0') - set a value (value != NULL && modifier == '\0') - add a value (value != NULL && modifier == '+') - remove a value (value != NULL && modifier == '-') The real problem is that remove_fcn() behaves fundamentally different from set_fcn(). You can do "+setting.property value1,value2" but you cannot remove them the same way. That is because most remove_fcn() implementations don't expect a list of values. But it's also because of the unnatural split between set_fcn() and remove_fcn(). The next commit will merge set_fcn(), remove_fcn() and reset property. This commit just merges them all in nmc_setting_set_property().		2019-03-25 09:12:32 +01:00
..
cli	cli: merge remove-property, reset-property and set-property	2019-03-25 09:12:32 +01:00
common	cli: don't interpret value as index too early for nmc_setting_remove_property_option()	2019-03-25 09:12:32 +01:00
tests	cli/tests: fix cli tests after changing Polish translations	2019-02-25 16:20:59 +01:00
tui	libnm,core: use _nm_utils_ascii_str_to_uint64() instead of strtol()	2019-02-12 08:50:28 +01:00
meson.build	build: meson: Add trailing commas	2018-12-20 13:50:34 +01:00
nm-online.c	nm-online: sort options in man page and program help	2018-11-05 09:32:20 +01:00