delta/NetworkManager.git/man/nmcli.xml, branch th/fix-python-test gitlab.freedesktop.org: NetworkManager/NetworkManager.git cli: add kill switch indication to "nmcli" output 2019-09-20T10:49:21+00:00 Lubomir Rintel lkundrak@v3.sk 2019-09-12T07:51:06+00:00 25fadf8f92a1d02c19c657beddbed54900d3baaa There is some guess work done on the client side. Perhaps the o.fd.NM.Device could be extended to indicate which kill switch is the device disabled by. This could be good enough for now though. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/271/commits 
There is some guess work done on the client side. Perhaps the
o.fd.NM.Device could be extended to indicate which kill switch is the
device disabled by. This could be good enough for now though.

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/271/commits
man/cli: better explain modifying properties regarding +/- modifiers 2019-08-16T06:16:02+00:00 Thomas Haller thaller@redhat.com 2019-08-12T13:57:14+00:00 cec39d76bdad0c9ad4281cae54c98b89b55fa2b8 






man: update reference for reporting bugs in `man nmcli`
2019-06-11T11:26:19+00:00

Thomas Haller
thaller@redhat.com

2019-06-11T10:46:52+00:00

a530921f401f78106ffdbe3ff59021ff696cb95a

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





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







all: fix misspellings
2019-01-24T16:19:44+00:00

Rafael Fontenelle
rafaelff@gnome.org

2019-01-11T19:07:03+00:00

d81e10942fda8b6cb163fc1d631cd44eb35e3b91

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





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







merge: branch 'master' of https://github.com/balrog-kun/NetworkManager
2019-01-04T17:26:41+00:00

Lubomir Rintel
lkundrak@v3.sk

2019-01-04T17:26:41+00:00

96782b94e185efe5eb9f8d11637b07b316c9d820

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





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







cli: reuse connections in nmcli dev wifi con
2018-12-04T13:46:37+00:00

Andrew Zaborowski
andrew.zaborowski@intel.com

2018-06-12T04:52:01+00:00

35932375272a7f723b63017a8524d91ff7113edc

Try to locate an existing connection before creating a new one when
handling "nmcli device wifi connect".  This allows WPA-Enterprise
networks to be activated this way, consistent with the comment that this
command is equivalent to clicking on an SSID in a GUI client.





Try to locate an existing connection before creating a new one when
handling "nmcli device wifi connect".  This allows WPA-Enterprise
networks to be activated this way, consistent with the comment that this
command is equivalent to clicking on an SSID in a GUI client.







all: say Wi-Fi instead of "wifi" or "WiFi"
2018-11-29T16:53:35+00:00

Lubomir Rintel
lkundrak@v3.sk

2018-11-21T10:32:38+00:00

b385ad015944af4349b56ffe38ab6369f78655b9

Correct the spelling across the *entire* tree, including translations,
comments, etc. It's easier that way.

Even the places where it's not exposed to the user, such as tests, so
that we learn how is it spelled correctly.





Correct the spelling across the *entire* tree, including translations,
comments, etc. It's easier that way.

Even the places where it's not exposed to the user, such as tests, so
that we learn how is it spelled correctly.







man: fix typo in nmcli manual
2018-11-14T17:26:07+00:00

Thomas Haller
thaller@redhat.com

2018-11-14T17:25:29+00:00

89bd19b0d7b194c7e249d8369c5e7d25ffaeb65e

Fixes: 17f9801e07df0c544e0416c65cedc28727476e55





Fixes: 17f9801e07df0c544e0416c65cedc28727476e55







man: add an early reference to nmcli-examples in nmcli man page
2018-11-14T16:15:55+00:00

Francesco Giudici
fgiudici@redhat.com

2018-11-14T16:15:55+00:00

2f2ad4d92528ca73b04e03dcbeca01bf9b073aeb












man: clarify blocking autoconnect during `nmcli connection down`
2018-11-13T12:48:10+00:00

Thomas Haller
thaller@redhat.com

2018-11-13T11:30:27+00:00

17f9801e07df0c544e0416c65cedc28727476e55

Manually disconnecting a profile of course blocks autoconnect of the
same profile. Otherwise, the profile would likely re-activate right
away, which is clearly against the users intention. If the users just
want to re-activate the profile, they should issue `nmcli connection up`
instead, with does a full down and up cycle.

This is more interesting for profiles that have 'connection.multi-connect'
set to 'multiple'. Would you expect that manually deactivating such a
profile blocks autoconnect of the profile on all devices? Maybe
yes, maybe not. Currently that is indeed the case and autoconnect gets
blocked regardless of multi-connect.





Manually disconnecting a profile of course blocks autoconnect of the
same profile. Otherwise, the profile would likely re-activate right
away, which is clearly against the users intention. If the users just
want to re-activate the profile, they should issue `nmcli connection up`
instead, with does a full down and up cycle.

This is more interesting for profiles that have 'connection.multi-connect'
set to 'multiple'. Would you expect that manually deactivating such a
profile blocks autoconnect of the profile on all devices? Maybe
yes, maybe not. Currently that is indeed the case and autoconnect gets
blocked regardless of multi-connect.