[git] set git.diff.renameLimit.infinity=false to deal with git index performance problems

On some projects, setting diff.renameLimit to infinity results in git log indexing process to run for several hours and consume a lot of memory. To deal with this problem, we have to turn this option off.
Unfortunately, this results in incomplete history for files that were renamed as a part of a large move (>1k files). We have to fix this problem separately in the future.

diff.renameLimit=0 was first introduced in de41656b7c

IDEA-170443 (indexing), IDEA-123397 (file history through commits with big renames)
This commit is contained in:
Julia Beliaeva
2017-03-27 18:12:36 +03:00
parent 0e48b2a0f6
commit f04c9cc2cd
@@ -851,7 +851,7 @@ git.file.history.full=true
git.file.history.full.description=Adds "--full-history --simplify-merges" to git log arguments when retrieving history for a file. \
This may sometimes result in empty merges being shown in the file history. \
However, skipping this arguments hides some side branches if the end result is the same.
git.diff.renameLimit.infinity=true
git.diff.renameLimit.infinity=false
git.diff.renameLimit.infinity.description=Sets diff.renameLimit configuration variable to zero. \
Essentially this variable tells Git the maximal size of commit for which perform rename detection.\
Switching this option on may lead to increased memory consumption by a Git process.\