TortoiseGitBlame does not follow renames when comparing line with previous version
By nao... on November 12, 2013 23:18 (imported from Google Code)
What steps will reproduce the problem?
- Move a bunch of files through 'git mv', commit.
- Blame any of those files. The log at the bottom shows the full history.
- Right-click any SHA1 on the left, click 'Blame previous revision'
What is the expected output?
A new TortoiseGitBlame window with the requested changeset.
What do you see instead?
fatal: no such path (my file name) in (my old commit ID)"
It does that for any files that were moved with git mv, including files in a folder where only the case ('Sources') was modified ('sources'). Root files (which were not moved) work just fine. Clicking the bottom part of the window to access an older commit also works, but it doesn't keep the current position in the file, and it's not very practical.
What version of TortoiseGit and msysgit are you using? On
what operating system?
TortoiseGitBlame 1.8.6, git version 1.8.4.msysgit.0, Windows 7 64-bit French.
Please provide any additional information below.
http://wedge.org/pub/8299/git-problems-for-non-gits/ (just a longer version of this issue.)