* [PATCH BlueZ] tools/mesh-cfgclient: fix binaries and config name in README
@ 2019-11-07 12:16 Aurelien Jarno
2019-11-07 17:24 ` Gix, Brian
0 siblings, 1 reply; 2+ messages in thread
From: Aurelien Jarno @ 2019-11-07 12:16 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Aurelien Jarno
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH BlueZ] tools/mesh-cfgclient: fix binaries and config name in README
2019-11-07 12:16 [PATCH BlueZ] tools/mesh-cfgclient: fix binaries and config name in README Aurelien Jarno
@ 2019-11-07 17:24 ` Gix, Brian
0 siblings, 0 replies; 2+ messages in thread
From: Gix, Brian @ 2019-11-07 17:24 UTC (permalink / raw)
To: aurelien@aurel32.net, linux-bluetooth@vger.kernel.org
Applied
On Thu, 2019-11-07 at 13:16 +0100, Aurelien Jarno wrote:
> 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-11-07 17:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-11-07 12:16 [PATCH BlueZ] tools/mesh-cfgclient: fix binaries and config name in README Aurelien Jarno
2019-11-07 17:24 ` Gix, Brian
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).