summaryrefslogtreecommitdiff
path: root/po
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2018-04-13 22:32:59 +0200
committerThomas Haller <thaller@redhat.com>2018-04-19 09:36:41 +0200
commit21f6058cfee6e1eee94b770bf78b690054b2928a (patch)
tree64f8216323f74221c4ef237c376fa3d5c33b502a /po
parentf99dc6b936eeb352c0a79a3d7208753eba8e7695 (diff)
downloadNetworkManager-21f6058cfee6e1eee94b770bf78b690054b2928a.tar.gz
libnm/keyfile: merge keyfile sources (pt2, merge nm-keyfile-writer.c)
Splitting keyfile handling in two "reader.c" and "writer.c" files is not helpful. What is most interesting, is to see how property XYZ is serialized to keyfile, and to verify that the parser does the inverse. For that, it's easier if both the write_xzy() and parse_xyz() function are beside each other, and not split accross files. The more important reason is, that both reader and writer have their separate handler arrays, for special handling of certain properties: @key_parsers and @key_writers. These two should not be separate but will be merged. Since they reference static functions, these functions must all be in the same source file (unless, we put them into headers, which would be unnecessary complex). No code was changed, only moved.
Diffstat (limited to 'po')
-rw-r--r--po/POTFILES.in1
1 files changed, 0 insertions, 1 deletions
diff --git a/po/POTFILES.in b/po/POTFILES.in
index 6451228191..ed492ba11e 100644
--- a/po/POTFILES.in
+++ b/po/POTFILES.in
@@ -56,7 +56,6 @@ libnm-core/crypto_nss.c
libnm-core/nm-connection.c
libnm-core/nm-dbus-utils.c
libnm-core/nm-keyfile.c
-libnm-core/nm-keyfile-writer.c
libnm-core/nm-setting-8021x.c
libnm-core/nm-setting-adsl.c
libnm-core/nm-setting-bluetooth.c