Hi, Arnaldo :)
On 06/23/2016 08:56 PM, Arnaldo Carvalho de Melo wrote:
Em Thu, Jun 23, 2016 at 05:55:18PM +0900, Taeung Song escreveu:
Many sub-commands use perf_config() but
everytime perf_config() is called, perf_config() always read config files.
(i.e. user config '~/.perfconfig' and system
Hi, Arnaldo :)
On 06/23/2016 08:56 PM, Arnaldo Carvalho de Melo wrote:
Em Thu, Jun 23, 2016 at 05:55:18PM +0900, Taeung Song escreveu:
Many sub-commands use perf_config() but
everytime perf_config() is called, perf_config() always read config files.
(i.e. user config '~/.perfconfig' and system
Em Thu, Jun 23, 2016 at 05:55:18PM +0900, Taeung Song escreveu:
> Many sub-commands use perf_config() but
> everytime perf_config() is called, perf_config() always read config files.
> (i.e. user config '~/.perfconfig' and system config
> '$(sysconfdir)/perfconfig')
>
> But it is better to use
Em Thu, Jun 23, 2016 at 05:55:18PM +0900, Taeung Song escreveu:
> Many sub-commands use perf_config() but
> everytime perf_config() is called, perf_config() always read config files.
> (i.e. user config '~/.perfconfig' and system config
> '$(sysconfdir)/perfconfig')
>
> But it is better to use
Many sub-commands use perf_config() but
everytime perf_config() is called, perf_config() always read config files.
(i.e. user config '~/.perfconfig' and system config '$(sysconfdir)/perfconfig')
But it is better to use the config set that already contains all config
key-value pairs to avoid this
Many sub-commands use perf_config() but
everytime perf_config() is called, perf_config() always read config files.
(i.e. user config '~/.perfconfig' and system config '$(sysconfdir)/perfconfig')
But it is better to use the config set that already contains all config
key-value pairs to avoid this
6 matches
Mail list logo