summaryrefslogtreecommitdiff
path: root/Documentation/RelNotes/1.7.8.3.txt
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2012-09-11 14:30:03 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-09-11 14:30:03 -0700
commit9aeaab6811dce596b4f6141d76f5300359bfd009 (patch)
treecb2e3cd727dbb35eef5a422a8c6b540b1af476ac /Documentation/RelNotes/1.7.8.3.txt
parentblame $path: avoid getting fooled by case insensitive filesystems (diff)
downloadtgif-9aeaab6811dce596b4f6141d76f5300359bfd009.tar.xz
blame: allow "blame file" in the middle of a conflicted merge
"git blame file" has always meant "find the origin of each line of the file in the history leading to HEAD, oh by the way, blame the lines that are modified locally to the working tree". This teaches "git blame" that during a conflicted merge, some uncommitted changes may have come from the other history that is being merged. The verify_working_tree_path() function introduced in the previous patch to notice a typo in the filename (primarily on case insensitive filesystems) has been updated to allow a filename that does not exist in HEAD (i.e. the tip of our history) as long as it exists one of the commits being merged, so that a "we deleted, the other side modified" case tracks the history of the file in the history of the other side. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes/1.7.8.3.txt')
0 files changed, 0 insertions, 0 deletions