On Mon, Oct 16 2017, Junio C. Hamano jotted:
> Christian Couder writes:
>
>> It is error prone and tiring to use many long environment
>> variables to give parameters to the 'run' script.
>
> This topic has been sitting in the list archive without getting much
> reaction from list participants.
On Mon, Oct 16, 2017 at 7:25 AM, Junio C Hamano wrote:
> Christian Couder writes:
>
>> It is error prone and tiring to use many long environment
>> variables to give parameters to the 'run' script.
>
> This topic has been sitting in the list archive without getting much
> reaction from list parti
On Wed, Oct 18, 2017 at 12:58 PM, Kevin Daudt wrote:
> On Sat, Sep 23, 2017 at 07:55:56PM +, Christian Couder wrote:
>> diff --git a/t/perf/run b/t/perf/run
>> index beb4acc0e428d..1e7c2a59e45dc 100755
>> --- a/t/perf/run
>> +++ b/t/perf/run
>> @@ -2,9 +2,14 @@
>>
>> case "$1" in
>> --
On Sat, Sep 23, 2017 at 07:55:56PM +, Christian Couder wrote:
> It is error prone and tiring to use many long environment
> variables to give parameters to the 'run' script.
>
> Let's make it easy to store some parameters in a config
> file and to pass them to the run script.
>
> The GIT_PERF
Christian Couder writes:
> It is error prone and tiring to use many long environment
> variables to give parameters to the 'run' script.
This topic has been sitting in the list archive without getting much
reaction from list participants. Is anybody happy with these
patches?
It is error prone and tiring to use many long environment
variables to give parameters to the 'run' script.
Let's make it easy to store some parameters in a config
file and to pass them to the run script.
The GIT_PERF_CONFIG_FILE variable will be set to the
argument of the '--config' option. This
6 matches
Mail list logo