summaryrefslogtreecommitdiff
path: root/t/t4135-apply-weird-filenames.sh
diff options
context:
space:
mode:
authorLibravatar Mike Hommey <mh@glandium.org>2016-07-16 08:23:45 +0900
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-07-18 14:33:38 -0700
commit3b75ee93278179004bc2f117fcfe3d5d76a0a2fa (patch)
tree86f8d5603b6030f76206ec1f1beac1eb3d6ff45b /t/t4135-apply-weird-filenames.sh
parentGit 2.8.4 (diff)
downloadtgif-3b75ee93278179004bc2f117fcfe3d5d76a0a2fa.tar.xz
blame: allow to blame paths freshly added to the index
When blaming files, changes in the work tree are taken into account and displayed as being "Not Committed Yet". However, when blaming a file that is not known to the current HEAD, git blame fails with `no such path 'foo' in HEAD`, even when the file was git add'ed. Allowing such a blame is useful when the new file added to the index (not yet committed) was created by renaming an existing file. It also is useful when the new file was created from pieces already in HEAD, moved or copied from other files and blaming with copy detection (i.e. "-C"). Signed-off-by: Mike Hommey <mh@glandium.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4135-apply-weird-filenames.sh')
0 files changed, 0 insertions, 0 deletions