summaryrefslogtreecommitdiff
path: root/write_or_die.c
diff options
context:
space:
mode:
authorLibravatar Bo Yang <struggleyb.nku@gmail.com>2010-05-06 21:52:28 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2010-05-07 09:34:28 -0700
commit1da6175d438a9849db07a68326ee05f291510074 (patch)
tree1c2cc5a775f5c8f153a7e27e6bbb84a80ef16401 /write_or_die.c
parentAdd a macro DIFF_QUEUE_CLEAR. (diff)
downloadtgif-1da6175d438a9849db07a68326ee05f291510074.tar.xz
Make diffcore_std only can run once before a diff_flush
When file renames/copies detection is turned on, the second diffcore_std will degrade a 'C' pair to a 'R' pair. And this may happen when we run 'git log --follow' with hard copies finding. That is, the try_to_follow_renames() will run diffcore_std to find the copies, and then 'git log' will issue another diffcore_std, which will reduce 'src->rename_used' and recognize this copy as a rename. This is not what we want. So, I think we really don't need to run diffcore_std more than one time. Signed-off-by: Bo Yang <struggleyb.nku@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'write_or_die.c')
0 files changed, 0 insertions, 0 deletions