On Fri, Nov 13, 2015 at 12:47 PM, Jens Lehmann wrote:
> Am 12.11.2015 um 00:34 schrieb Stefan Beller:
>>
>> On Wed, Nov 11, 2015 at 11:55 AM, Jens Lehmann
>> wrote:
TL;DR: checkout is serial, network-related stuff only will be using
submodule.jobs
>>>
>>>
>>>
>>> My point bein
Am 12.11.2015 um 00:34 schrieb Stefan Beller:
On Wed, Nov 11, 2015 at 11:55 AM, Jens Lehmann wrote:
TL;DR: checkout is serial, network-related stuff only will be using
submodule.jobs
My point being: isn't "jobs" a bit too generic for a config option that
is only relevant for network-related
On Wed, Nov 11, 2015 at 11:55 AM, Jens Lehmann wrote:
>>
>> TL;DR: checkout is serial, network-related stuff only will be using
>> submodule.jobs
>
>
> My point being: isn't "jobs" a bit too generic for a config option that
> is only relevant for network-related stuff? Maybe "submodule.fetchJobs"
Am 10.11.2015 um 23:29 schrieb Stefan Beller:
On Tue, Nov 10, 2015 at 2:21 PM, Jens Lehmann wrote:
+submodule.jobs::
+ This is used to determine how many submodules can be operated on in
+ parallel. Specifying a positive integer allows up to that number
+ of submodules being f
On Tue, Nov 10, 2015 at 2:21 PM, Jens Lehmann wrote:
>> +submodule.jobs::
>> + This is used to determine how many submodules can be operated on in
>> + parallel. Specifying a positive integer allows up to that number
>> + of submodules being fetched in parallel. This is used in f
Am 04.11.2015 um 01:37 schrieb Stefan Beller:
This allows to configure fetching and updating in parallel
without having the command line option.
This moved the responsibility to determine how many parallel processes
to start from builtin/fetch to submodule.c as we need a way to communicate
"The
This allows to configure fetching and updating in parallel
without having the command line option.
This moved the responsibility to determine how many parallel processes
to start from builtin/fetch to submodule.c as we need a way to communicate
"The user did not specify the number of parallel proc
7 matches
Mail list logo