summaryrefslogtreecommitdiff
path: root/t/t5100/patch0004
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2011-02-19 05:20:51 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2011-02-21 10:21:26 -0800
commitbf0ab10fa84df6c49450a06077d1c52756d88222 (patch)
tree0722540155c202e474b59de2fa41db1e740a4bbd /t/t5100/patch0004
parentGit 1.7.4 (diff)
downloadtgif-bf0ab10fa84df6c49450a06077d1c52756d88222.tar.xz
merge: improve inexact rename limit warning
The warning is generated deep in the diffcore code, which means that it will come first, followed possibly by a spew of conflicts, making it hard to see. Instead, let's have diffcore pass back the information about how big the rename limit would needed to have been, and then the caller can provide a more appropriate message (and at a more appropriate time). No refactoring of other non-merge callers is necessary, because nobody else was even using the warn_on_rename_limit feature. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5100/patch0004')
0 files changed, 0 insertions, 0 deletions