summaryrefslogtreecommitdiff
path: root/git-merge-one-file.sh
diff options
context:
space:
mode:
authorLibravatar David Kastrup <dak@gnu.org>2019-04-02 13:56:25 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-04-03 16:45:26 +0900
commitf89201494308524a92eff5995d122e8553c36508 (patch)
treed8b50bf3f6a35908053acd90eb73ebcab019b488 /git-merge-one-file.sh
parentmingw: allow building with an MSYS2 runtime v3.x (diff)
downloadtgif-f89201494308524a92eff5995d122e8553c36508.tar.xz
blame.c: don't drop origin blobs as eagerly
When a parent blob already has chunks queued up for blaming, dropping the blob at the end of one blame step will cause it to get reloaded right away, doubling the amount of I/O and unpacking when processing a linear history. Keeping such parent blobs in memory seems like a reasonable optimization that should incur additional memory pressure mostly when processing the merges from old branches. Signed-off-by: David Kastrup <dak@gnu.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-merge-one-file.sh')
0 files changed, 0 insertions, 0 deletions