summaryrefslogtreecommitdiff
path: root/clients/cli/nmcli-completion
diff options
context:
space:
mode:
authorFrancesco Giudici <fgiudici@redhat.com>2016-04-18 18:50:56 +0200
committerFrancesco Giudici <fgiudici@redhat.com>2016-04-28 09:35:20 +0200
commit3c67a1ec5e8ef35169bba961faff6bfdfacc1cfa (patch)
treead5133335bf887128c6e4f0ec09b51c593df4f63 /clients/cli/nmcli-completion
parent0589e659ca1aab76be9ca11e705bef56c3b03f45 (diff)
downloadNetworkManager-3c67a1ec5e8ef35169bba961faff6bfdfacc1cfa.tar.gz
cli: remove version check against NM
When performing NM package upgrade the new version of nmcli will be immediately available while NM daemon will not, as it would not restart in order to avoid to disrupt connectivity. This could create issues with tools leveraging on nmcli output (till reboot). As apart from this case it is very unlikely that a user can have this nmcli / NM daemon version mismatch situation, the check could cause more harm than benefit in real user case scenarios. https://bugzilla.redhat.com/show_bug.cgi?id=1291785
Diffstat (limited to 'clients/cli/nmcli-completion')
-rw-r--r--clients/cli/nmcli-completion5
1 files changed, 1 insertions, 4 deletions
diff --git a/clients/cli/nmcli-completion b/clients/cli/nmcli-completion
index 7f79180f43..1b1dce3322 100644
--- a/clients/cli/nmcli-completion
+++ b/clients/cli/nmcli-completion
@@ -178,9 +178,6 @@ _nmcli_compl_OPTIONS()
pretty)
_nmcli_array_delete_at words 0
;;
- nocheck)
- _nmcli_array_delete_at words 0
- ;;
ask)
_nmcli_array_delete_at words 0
;;
@@ -804,7 +801,7 @@ _nmcli()
local COMMAND_CONNECTION_ACTIVE=""
HELP_ONLY_AS_FIRST=
- local LONG_OPTIONS=(terse pretty mode fields colors escape nocheck ask show-secrets wait version help)
+ local LONG_OPTIONS=(terse pretty mode fields colors escape ask show-secrets wait version help)
_nmcli_compl_OPTIONS
i=$?