> On 04 Oct 2017, at 13:55, Junio C Hamano wrote:
>
> Lars Schneider writes:
>
>>> The delayed progress API is being simplified so I'll probably do a
>>> bit of evil merge while merging this to 'pu'.
>>
>> I just realized that this patch got lost
Lars Schneider writes:
>> The delayed progress API is being simplified so I'll probably do a
>> bit of evil merge while merging this to 'pu'.
>
> I just realized that this patch got lost :-(
Really? Isn't it 52f1d62e ("convert: display progress for filtered
objects
> On 04 Oct 2017, at 12:52, Lars Schneider wrote:
>
>
>> On 24 Aug 2017, at 21:40, Junio C Hamano wrote:
>>
>> Lars Schneider writes:
>>
>>> In 2841e8f ("convert: add "status=delayed" to filter process protocol",
>>>
> On 24 Aug 2017, at 21:40, Junio C Hamano wrote:
>
> Lars Schneider writes:
>
>> In 2841e8f ("convert: add "status=delayed" to filter process protocol",
>> 2017-06-30) we taught the filter process protocol to delayed responses.
>> These responses
Lars Schneider writes:
> In 2841e8f ("convert: add "status=delayed" to filter process protocol",
> 2017-06-30) we taught the filter process protocol to delayed responses.
> These responses are processed after the "Checking out files" phase.
> If the processing takes
In 2841e8f ("convert: add "status=delayed" to filter process protocol",
2017-06-30) we taught the filter process protocol to delayed responses.
These responses are processed after the "Checking out files" phase.
If the processing takes noticeable time, then the user might think Git
is stuck.
6 matches
Mail list logo