On Sat, Nov 3, 2018 at 1:38 AM Junio C Hamano wrote:
>
> Duy Nguyen writes:
>
> > On Fri, Nov 2, 2018 at 2:32 PM Ben Peart wrote:
> >>
> >> From: Ben Peart
> >>
> >> During an "add", a call is made to run_diff_files() which calls
> >> check_remove() for each index-entry. The preload_index() co
Duy Nguyen writes:
> On Fri, Nov 2, 2018 at 2:32 PM Ben Peart wrote:
>>
>> From: Ben Peart
>>
>> During an "add", a call is made to run_diff_files() which calls
>> check_remove() for each index-entry. The preload_index() code distributes
>> some of the costs across multiple threads.
>
> Instea
On 11/2/2018 11:23 AM, Junio C Hamano wrote:
Ben Peart writes:
From: Ben Peart
During an "add", a call is made to run_diff_files() which calls
check_remove() for each index-entry. The preload_index() code
distributes some of the costs across multiple threads.
Nice. I peeked around and
On Fri, Nov 2, 2018 at 2:32 PM Ben Peart wrote:
>
> From: Ben Peart
>
> During an "add", a call is made to run_diff_files() which calls
> check_remove() for each index-entry. The preload_index() code distributes
> some of the costs across multiple threads.
Instead of doing this site by site. Ho
Ben Peart writes:
> From: Ben Peart
>
> During an "add", a call is made to run_diff_files() which calls
> check_remove() for each index-entry. The preload_index() code
> distributes some of the costs across multiple threads.
Nice. I peeked around and noticed that we already do this in
builtin
From: Ben Peart
During an "add", a call is made to run_diff_files() which calls
check_remove() for each index-entry. The preload_index() code distributes
some of the costs across multiple threads.
Because the files checked are restricted to pathspec, adding individual
files makes no measurable
6 matches
Mail list logo