Due to a huge scale file renaming action across branches (don’t ask), we have a few files where we can only see the full history when we use git log --follow
.
git gui blame
by default follows through that rename, but Sublime Merge blame doesn’t.
Due to a huge scale file renaming action across branches (don’t ask), we have a few files where we can only see the full history when we use git log --follow
.
git gui blame
by default follows through that rename, but Sublime Merge blame doesn’t.