Re: [PATCH v3] add status config and command line options for rename detection

On 5/12/2018 4:04 AM, Eckhard Maaß wrote: On Fri, May 11, 2018 at 12:56:39PM +, Ben Peart wrote: After performing a merge that has conflicts git status will, by default, attempt to detect renames which causes many objects to be examined. In a virtualized repo, those objects do not exist

Re: [PATCH v3] add status config and command line options for rename detection

On Fri, May 11, 2018 at 12:56:39PM +, Ben Peart wrote: > After performing a merge that has conflicts git status will, by default, > attempt to detect renames which causes many objects to be examined. In a > virtualized repo, those objects do not exist locally so the rename logic > triggers

Re: [PATCH v3] add status config and command line options for rename detection

Hi Ben, On Fri, May 11, 2018 at 5:56 AM, Ben Peart wrote: > After performing a merge that has conflicts git status will, by default, > attempt to detect renames which causes many objects to be examined. In a > virtualized repo, those objects do not exist locally so the

[PATCH v3] add status config and command line options for rename detection

After performing a merge that has conflicts git status will, by default, attempt to detect renames which causes many objects to be examined. In a virtualized repo, those objects do not exist locally so the rename logic triggers them to be fetched from the server. This results in the status call