summaryrefslogtreecommitdiff
path: root/t/t5515/refs.br-remote-glob-merge_remote-glob
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2012-09-21 13:52:25 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-09-21 13:52:25 -0700
commit3d1aa56671e7f33740dcd2cf0642d5ce09bd6a95 (patch)
tree47812eabc3ec1c53def5bb11aba989258adfeed7 /t/t5515/refs.br-remote-glob-merge_remote-glob
parentdiff: accept --no-follow option (diff)
downloadtgif-3d1aa56671e7f33740dcd2cf0642d5ce09bd6a95.tar.xz
blame: pay attention to --no-follow
If you know your history did not have renames, or if you care only about the history after a large rename that happened some time ago, "git blame --no-follow $path" is a way to tell the command not to bother about renames. When you use -C, the lines that came from the renamed file will still be found without the whole-file rename detection, so it is not all that interesting either way, though. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/refs.br-remote-glob-merge_remote-glob')
0 files changed, 0 insertions, 0 deletions