Re: [PATCH on en/rename-progress] diffcore-rename: make diff-tree -l0 mean -l

Elijah Newren wrote: > On Wed, Nov 29, 2017 at 10:32 AM, Jonathan Tan > wrote: >> In the documentation of diff-tree, it is stated that the -l option >> "prevents rename/copy detection from running if the number of >> rename/copy targets exceeds the specified number".

Re: [PATCH on en/rename-progress] diffcore-rename: make diff-tree -l0 mean -l

On Wed, 29 Nov 2017 10:51:20 -0800 Elijah Newren wrote: > Thanks for testing that version and sending along the fix. > > I suspect the commit referenced twice in the commit message should > have been 9f7e4bfa3b ("diff: remove silent clamp of renameLimit", > 2017-11-13) rather

Re: [PATCH on en/rename-progress] diffcore-rename: make diff-tree -l0 mean -l

On Wed, Nov 29, 2017 at 10:32 AM, Jonathan Tan wrote: > In the documentation of diff-tree, it is stated that the -l option > "prevents rename/copy detection from running if the number of > rename/copy targets exceeds the specified number". The documentation > does not

[PATCH on en/rename-progress] diffcore-rename: make diff-tree -l0 mean -l

In the documentation of diff-tree, it is stated that the -l option "prevents rename/copy detection from running if the number of rename/copy targets exceeds the specified number". The documentation does not mention any special handling for the number 0, but the implementation before commit b520abf