- 27 Oct, 2015 1 commit
-
-
- 15 Jul, 2014 1 commit
-
-
Dan Winship authored
- Remove list of authors from files that had them; these serve no purpose except to quickly get out of date (and were only used in libnm-util and not libnm-glib anyway). - Just say "Copyright", not "(C) Copyright" or "Copyright (C)" - Put copyright statement after the license, not before - Remove "NetworkManager - Network link manager" from the few files that contained it, and "libnm_glib -- Access network status & information from glib applications" from the many files that contained it. - Remove vim modeline from nm-device-olpc-mesh.[ch], add emacs modeline to files that were missing it.
-
- 19 Jun, 2014 1 commit
-
-
Dan Winship authored
We made the UIs consistent last year, but missed the documentation. Fix the docs to also consistently use "Wi-Fi" rather than "WiFi", "Wifi", "wifi", or "WiFI"; "Ethernet" rather than "ethernet"; and "InfiniBand" rather than "Infiniband".
-
- 28 Feb, 2014 1 commit
-
-
Jiří Klimeš authored
nm_setting_vlan_remove_priority_by_value() nm_setting_vlan_remove_priority_str_by_value()
-
- 03 Apr, 2013 1 commit
-
-
Dan Winship authored
Ignoring carrier is generally something you want at the machine level (eg, for a server), not at the connection level.
-
- 15 Feb, 2013 1 commit
-
-
Dan Winship authored
For settings corresponding to devices that have a :carrier property (ie bond, bridge, infiniband, vlan, and wired), add a :carrier-detect property specifying how that affects the connection: yes: The connection can only be activated when the device has carrier, and will be deactivated if the device loses carrier (for more than 4 seconds). no: The connection ignores carrier on the device; it can be activated when there is no carrier, and stays activated when carrier is lost. on-activate: The connection can only be activated when the device has carrier, but it will not be deactivated if the device loses carrier. https://bugzilla.gnome.org/show_bug.cgi?id=688284
-
- 27 Sep, 2012 1 commit
-
-
Dan Winship authored
Do slightly more validation if NMSettingVlan properties, and make sure that at least one method of specifying a parent is used. Remove the check that id is in range, since gobject will not allow you to set the property to a value outside its declared range anyway.
-
- 27 Jul, 2012 1 commit
-
-
Jiří Klimeš authored
The argument is 'klass' not 'obj'.
-
- 12 Mar, 2012 1 commit
-
-
Dan Winship authored
When NM was registering all of its enum types by hand, it was using NamesLikeThis rather than the default names-like-this for the "nick" values. When we switched to using glib-mkenums, this resulted in dbus-glib using different strings for the D-Bus error names, causing compatibility problems. Fix this by using glib-mkenums annotations to manually fix all the enum values back to what they were before. (This can't be done in a more automated way, because the old names aren't 100% consistent. Eg, "UNKNOWN" frequently becomes "UnknownError" rather than just "Unknown".)
-
- 01 Mar, 2012 1 commit
-
-
Dan Williams authored
-
- 16 Feb, 2012 2 commits
-
-
Dan Williams authored
Add documentation so the API spec generator can do something for the VLAN setting. Also enforce validation of the ingress and egress priority maps; 802.1D priorities are limited to values from 0 - 7 and Linux SKB values are 32 bits. Also, the 'slave' property is a duplicate of the 'master' property added to NMSettingConnection in the bonding work so we can get rid of it and use 'master' instead.
-
Weiping Pan authored
Signed-off-by:
Weiping Pan <wpan@redhat.com> (dcbw: formatting cleanups and priority map code simplifications)
-