summaryrefslogtreecommitdiff
path: root/Documentation/git-blame.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2016-06-14 17:46:06 (GMT)
committerJunio C Hamano <gitster@pobox.com>2016-06-14 19:12:15 (GMT)
commitd993ce1ed2f025708b0f78bed241466e35f1e8a0 (patch)
treeb5fcc45707d598f83f00b93474ec44e41a1ff271 /Documentation/git-blame.txt
parent0b65a8dbdb38962e700ee16776a3042beb489060 (diff)
downloadgit-d993ce1ed2f025708b0f78bed241466e35f1e8a0.zip
git-d993ce1ed2f025708b0f78bed241466e35f1e8a0.tar.gz
git-d993ce1ed2f025708b0f78bed241466e35f1e8a0.tar.bz2
blame: improve diagnosis for "--reverse NEW"
"git blame --reverse OLD..NEW -- PATH" tells us to start from the contents in PATH at OLD and observe how each line is changed while the history develops up to NEW, and report for each line the latest commit up to which the line survives in the original form. If you say "git blame --reverse NEW -- PATH" by mistake, we complain about the missing OLD, but we phrased it as "No commit to dig down to?" In this case, however, we are digging up from OLD, so say so. Signed-off-by: Junio C Hamano <gitster@pobox.com>
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 ba54175..16323eb 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