summaryrefslogtreecommitdiff
path: root/Documentation/git-blame.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2016-10-10 14:03:51 -0700
committerJunio C Hamano <gitster@pobox.com>2016-10-10 14:03:51 -0700
commit1172e16af07d6e15bca6398f0ded18a0ae7b9249 (patch)
tree24cfd020511f1b345d1890c7281651db080f43c5 /Documentation/git-blame.txt
parenta460ea4a3cb1dad253604b5e2aeaa161637453a9 (diff)
parente1d09701a4fa3a4d15dd005e2b698934e4ae9ae0 (diff)
downloadgit-1172e16af07d6e15bca6398f0ded18a0ae7b9249.tar.gz
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 'Documentation/git-blame.txt')
-rw-r--r--Documentation/git-blame.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt
index 9dccb3319b..fdc3aea30a 100644
--- a/Documentation/git-blame.txt
+++ b/Documentation/git-blame.txt
@@ -10,7 +10,7 @@ SYNOPSIS
[verse]
'git blame' [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-e] [-p] [-w] [--incremental]
[-L <range>] [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>]
- [--progress] [--abbrev=<n>] [<rev> | --contents <file> | --reverse <rev>]
+ [--progress] [--abbrev=<n>] [<rev> | --contents <file> | --reverse <rev>..<rev>]
[--] <file>
DESCRIPTION