Re: [PATCHv2 0/8] Expose the submodule parallelism to the user

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 29, 2015, 17:23 UTC
Message-ID: <xmqqh9l9si57.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAGZ79kYXrOFDqs5c-OYG2vRO9GY_aoD_GU1=TkRtOMaGC_GowA@mail.gmail.com>

Stefan Beller <sbeller@google.com> writes:

Show 14 quoted lines

> On Thu, Oct 29, 2015 at 6:19 AM, Ramsay Jones
> <ramsay@ramsayjones.plus.com> wrote:
>
>> Hmm, is there a way to _not_ fetch in parallel (override the
>> config) from the command line for a given command?
>>
>> ATB,
>> Ramsay Jones
>
> git config submodule.jobs 42
> git <foo> --jobs 1 # should run just one task, despite having 42 configured
>
> It does use the parallel processing machinery though, but with a maximum of
> one subcommand being spawned. Is that what you're asking?

With this patch, do we still keep a separate machinery that bypasses the parallel thing altogether in the first place?

I was hoping that the underlying parallel machinery is polished enough that using it with max=1 parallelism would be equivalent to serial execution. At least, that was my understanding of our goal, and back when we reviewed the previous "fetch --recurse-sub" series, my impression was we were already there.

And in that ideal endgame world, your "Give '-j1' from the command line" would be perfectly an acceptable answer ;-).

Thanks.