Re: [PATCH 2/2] tests: introduce --stress-jobs=

2019-03-03 Thread Johannes Schindelin
Hi, On Sun, 3 Mar 2019, SZEDER Gábor wrote: > On Sat, Mar 02, 2019 at 01:19:44PM -0800, Johannes Schindelin via > GitGitGadget wrote: > > The --stress option currently accepts an argument, but it is confusing > > to at least this user that the argument does not define the maximal > > number of s

Re: [PATCH 2/2] tests: introduce --stress-jobs=

2019-03-03 Thread SZEDER Gábor
On Sat, Mar 02, 2019 at 01:19:44PM -0800, Johannes Schindelin via GitGitGadget wrote: > The --stress option currently accepts an argument, but it is confusing > to at least this user that the argument does not define the maximal > number of stress iterations, but instead the number of jobs to run

Re: [PATCH 2/2] tests: introduce --stress-jobs=

2019-03-03 Thread Junio C Hamano
"Johannes Schindelin via GitGitGadget" writes: > From: Johannes Schindelin > > The --stress option currently accepts an argument, but it is confusing > to at least this user that the argument does not define the maximal > number of stress iterations, but instead the number of jobs to run in > pa

Re: [PATCH 2/2] tests: introduce --stress-jobs=

2019-03-02 Thread Eric Sunshine
On Sat, Mar 2, 2019 at 4:19 PM Johannes Schindelin via GitGitGadget wrote: > The --stress option currently accepts an argument, but it is confusing > to at least this user that the argument does not define the maximal > number of stress iterations, but instead the number of jobs to run in > parall

[PATCH 2/2] tests: introduce --stress-jobs=

2019-03-02 Thread Johannes Schindelin via GitGitGadget
From: Johannes Schindelin The --stress option currently accepts an argument, but it is confusing to at least this user that the argument does not define the maximal number of stress iterations, but instead the number of jobs to run in parallel per stress iteration. Let's introduce a separate opt