summaryrefslogtreecommitdiff
path: root/Documentation/git-blame.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2007-01-17 13:04:15 -0800
committerJunio C Hamano <junkio@cox.net>2007-01-17 13:04:15 -0800
commit42f62db90575601680739116c833ad0c76bcc85d (patch)
treee3425f49ccc6f73a60a10e18e5ea5471d262f7e9 /Documentation/git-blame.txt
parent5cb545fa22fa590617c872e47568279218788d4b (diff)
downloadgit-42f62db90575601680739116c833ad0c76bcc85d.tar.gz
Documentation: m can be relative in "git-blame -Ln,m"
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/git-blame.txt')
-rw-r--r--Documentation/git-blame.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt
index b14e794077..5dd8e36bbd 100644
--- a/Documentation/git-blame.txt
+++ b/Documentation/git-blame.txt
@@ -118,9 +118,12 @@ SPECIFYING RANGES
Unlike `git-blame` and `git-annotate` in older git, the extent
of annotation can be limited to both line ranges and revision
ranges. When you are interested in finding the origin for
-ll. 40-60 for file `foo`, you can use `-L` option like this:
+ll. 40-60 for file `foo`, you can use `-L` option like these
+(they mean the same thing -- both ask for 21 lines starting at
+line 40):
git blame -L 40,60 foo
+ git blame -L 40,+21 foo
Also you can use regular expression to specify the line range.