delta/NetworkManager.git, branch bg/issue110

libnm-core: fix team link-watcher struct layout

2019-01-26T17:40:57+00:00

As the comment above the union says, structs in the union must have
the same layout of arp_ping. 'vlanid' is in the wrong place and breaks
that.

Fixes: f44c793f6cd89c3e84e83872478daf286821ed64

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/110

clients: update settings doc header file

2019-01-25T10:24:08+00:00

libnm-core: fix gtk-doc comment

2019-01-25T10:21:58+00:00

Fixes: d81e10942fda8b6cb163fc1d631cd44eb35e3b91

all: fix misspellings

2019-01-24T16:19:44+00:00

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/64

Merge branch 'master' into 'master'

2019-01-24T16:12:57+00:00

Update Ukrainian translation

See merge request NetworkManager/NetworkManager!66

Update Ukrainian translation

2019-01-24T13:25:43+00:00

po/de: fix typo

2019-01-24T07:32:48+00:00

https://github.com/NetworkManager/NetworkManager/pull/289

release: bump version to 1.15.2 (development)

2019-01-22T19:56:31+00:00

all: merge branch 'th/various-for-wireguard-1'

2019-01-22T15:31:59+00:00

https://github.com/NetworkManager/NetworkManager/pull/282

libnm: minor cleanup releasing setting from NMConnection

2019-01-22T15:30:23+00:00

There are two callers that are concerned with disconnecting/releasing a
setting:

 - _setting_release_hfr() (formerly _setting_release())

 - _nm_connection_add_setting() for the @s_old setting

Compared to one caller that connects/adds a setting (_nm_connection_add_setting()).

Refactor the two callers to use the same helper function
(_setting_release()) so that the implementation of how to release a
setting is at one place.

This patch was originally done when adding another signal to NMSetting.
That did not happen (yet), but the refactoring still makes sense.