mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-01-06 22:30:19 +01:00
Removing a setting that is not present should not be an error. The user asked that the profile doesn't have the requested setting, and that should succeed (even if that results in no actual change). Consider when you want to make a hotspot profile "open". That implies to remove the "wifi-sec" and "802-1x" settings. But you may not check before whether the profile is already open, and whether it already has those settings. We should just allow $ nmcli connection modify "$PROFILE" remove wifi-sec remove 802-1x to succeed, regardless whether this changes anything or not. Likewise, if you do $ nmcli connection modify "$PROFILE" con-name foo $ nmcli connection modify "$PROFILE" con-name foo then the second command doesn't fail with "the name is already \"foo\"". It just succeeds. |
||
|---|---|---|
| .. | ||
| agent.c | ||
| common.c | ||
| common.h | ||
| connections.c | ||
| connections.h | ||
| devices.c | ||
| devices.h | ||
| general.c | ||
| generate-docs-nm-settings-nmcli.c | ||
| generate-docs-nm-settings-nmcli.xml.in | ||
| meson.build | ||
| nmcli-completion | ||
| nmcli.c | ||
| nmcli.h | ||
| polkit-agent.c | ||
| polkit-agent.h | ||
| settings.c | ||
| settings.h | ||
| utils.c | ||
| utils.h | ||