summaryrefslogtreecommitdiff
path: root/t/t9126
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2016-10-10 14:03:51 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-10-10 14:03:51 -0700
commit1172e16af07d6e15bca6398f0ded18a0ae7b9249 (patch)
tree24cfd020511f1b345d1890c7281651db080f43c5 /t/t9126
parentMerge branch 'nd/shallow-deepen' (diff)
parentblame: dwim "blame --reverse OLD" as "blame --reverse OLD.." (diff)
downloadtgif-1172e16af07d6e15bca6398f0ded18a0ae7b9249.tar.xz
Merge branch 'jc/blame-reverse'
It is a common mistake to say "git blame --reverse OLD path", expecting that the command line is dwimmed as if asking how lines in path in an old revision OLD have survived up to the current commit. * jc/blame-reverse: blame: dwim "blame --reverse OLD" as "blame --reverse OLD.." blame: improve diagnosis for "--reverse NEW"
Diffstat (limited to 't/t9126')
0 files changed, 0 insertions, 0 deletions