Thomas Haller 66088a09b2 libnm: when stringifying policy routing rule place "not" specifier after "priority" ... Otherwise, it just looks odd: "not priority 31265 from 0.0.0.0/0 fwmark 0xcb87 table 52103" Better is: "priority 31265 not from 0.0.0.0/0 fwmark 0xcb87 table 52103" The "not" specifier should come after the priority. It makes more sense to read it that way. As far as parsing the string is concerned, the order does not matter. So this change in behavior is no problem. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/228		2019-08-05 10:16:10 +02:00
..
certs	libnm/crypto: accept TPM2-wrapped PEM keys	2019-07-10 17:31:48 +02:00
meson.build	build/meson: rename "nm_core_dep" to "libnm_core_dep"	2019-04-18 20:13:49 +02:00
nm-core-tests-enum-types.c.template	build: use template files for enum types' sources generation	2017-12-18 11:25:06 +01:00
nm-core-tests-enum-types.h.template	build: use template files for enum types' sources generation	2017-12-18 11:25:06 +01:00
test-compare.c	all: drop emacs file variables from source files	2019-06-11 10:04:00 +02:00
test-crypto.c	all: drop empty first line from sources	2019-06-11 10:15:06 +02:00
test-general-enums.h	all: drop emacs file variables from source files	2019-06-11 10:04:00 +02:00
test-general.c	libnm,cli,ifcfg-rh: add connection:wait-device-timeout property	2019-07-10 12:43:06 +02:00
test-keyfile.c	libnm/crypto: accept TPM2-wrapped PEM keys	2019-07-10 17:31:48 +02:00
test-secrets.c	libnm: fix setting error for nm_connection_update_secrets()	2019-06-26 12:26:11 +02:00
test-setting.c	libnm: when stringifying policy routing rule place "not" specifier after "priority"	2019-08-05 10:16:10 +02:00
test-settings-defaults.c	all: drop emacs file variables from source files	2019-06-11 10:04:00 +02:00