summaryrefslogtreecommitdiff
path: root/t/t9601/cvsroot/module
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2012-09-21 12:09:42 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-09-21 12:14:19 -0700
commite5dce96e9e26f8e30291c79fa5647313c64b2150 (patch)
tree6d97672b00d1778df96c99b962be6396b532407f /t/t9601/cvsroot/module
parentGit 1.7.11.7 (diff)
downloadtgif-e5dce96e9e26f8e30291c79fa5647313c64b2150.tar.xz
git blame: document that it always follows origin across whole-file renames
Make it clear to people who (rightly or wrongly) think that the "--follow" option should follow origin across while-file renames that we already do so. That would explain the output that they see when they do give the "--follow" option to the command. We may or may not want to do a "--no-follow" patch as a follow-up, but that is a separate topic. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9601/cvsroot/module')
0 files changed, 0 insertions, 0 deletions