Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Aurelien Jarno <aurelien@aurel32.net>
To:     linux-bluetooth@vger.kernel.org
Cc:     Aurelien Jarno <aurelien@aurel32.net>
Subject: [PATCH BlueZ] tools/mesh-cfgclient: fix binaries and config name in README
Date:   Thu,  7 Nov 2019 13:16:40 +0100
Message-Id: <20191107121640.26600-1-aurelien@aurel32.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

This patch fixes the mesh-cfgclient README file:
- The configuration directory is meshcfg not mesh-cfgcli
- The home directory is looked up using $HOME not using /home/$USER
- The binary is called mesh-cfgclient, not mesh-config
- The -c option takes a config file path, not the directory where the
  config file is stored.

---
 tools/mesh/README | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tools/mesh/README b/tools/mesh/README
index 9362d8ff6..3830d1b17 100644
--- a/tools/mesh/README
+++ b/tools/mesh/README
@@ -25,11 +25,11 @@ that contains information about the current state of the configured mesh
 network.
 
 The default directory for mesh-cfgclient configuration file is
-/home/<username>/.config/mesh-cfgcli
+$HOME/.config/meshcfg
 
-To specify a custom storage directory, run mesh-config tool as:
+To specify a custom file, run mesh-cfgclient tool as:
 
-	meshctl -c <config_dir_name>
+	mesh-cfgclient -c <config_file_name>
 
 If a configuration file is not found, it is assumed that a mesh network
 does not exist. In this case, the tool may be used to generate a new  mesh
-- 
2.24.0.rc1