diff options
author | Elijah Newren <newren@gmail.com> | 2017-11-13 12:15:59 -0800 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2017-11-15 13:11:25 +0900 |
commit | 9f7e4bfa3b6da16e3690312ff208cc27706b2c1b (patch) | |
tree | e53276ecfc9264ba8d57588291939e759c38b8ca /Documentation/technical | |
parent | progress: fix progress meters when dealing with lots of work (diff) | |
download | tgif-9f7e4bfa3b6da16e3690312ff208cc27706b2c1b.tar.xz |
diff: remove silent clamp of renameLimit
In commit 0024a5492 (Fix the rename detection limit checking; 2007-09-14),
the renameLimit was clamped to 32767. This appears to have been to simply
avoid integer overflow in the following computation:
num_create * num_src <= rename_limit * rename_limit
although it also could be viewed as a hardcoded bound on the amount of CPU
time we're willing to allow users to tell git to spend on handling
renames. An upper bound may make sense, but unfortunately this upper
bound was neither communicated to the users, nor documented anywhere.
Although large limits can make things slow, we have users who would be
ecstatic to have a small five file change be correctly cherry picked even
if they have to manually specify a large limit and wait ten minutes for
the renames to be detected.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/technical')
0 files changed, 0 insertions, 0 deletions