[PATCH] cli: fix description of --pin argument in --enable-pin help message

Ben Chan benchan at chromium.org
Thu Sep 26 00:37:10 PDT 2013


The original help message for --enable-pin implies that it expects the
existing PIN to be specified via the --pin argument, which seems
confusing as it actually expects the PIN to be set.
---
This is based on the conversation between Dan and me on IRC.

 cli/mmcli-sim.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cli/mmcli-sim.c b/cli/mmcli-sim.c
index 085f335..6441195 100644
--- a/cli/mmcli-sim.c
+++ b/cli/mmcli-sim.c
@@ -61,7 +61,7 @@ static GOptionEntry entries[] = {
       "[PUK]"
     },
     { "enable-pin", 0, 0, G_OPTION_ARG_NONE, &enable_pin_flag,
-      "Enable PIN request in a given SIM (must send the current PIN with --pin).",
+      "Enable PIN request in a given SIM (must send the new PIN with --pin).",
       NULL
     },
     { "disable-pin", 0, 0, G_OPTION_ARG_NONE, &disable_pin_flag,
-- 
1.8.4



More information about the ModemManager-devel mailing list