Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
Documentation: m can be relative in "git-blame -Ln,m"
author
Junio C Hamano
<junkio@cox.net>
Wed, 17 Jan 2007 21:04:15 +0000
(13:04 -0800)
committer
Junio C Hamano
<junkio@cox.net>
Wed, 17 Jan 2007 21:04:15 +0000
(13:04 -0800)
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-blame.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
5cb545f
)
diff --git
a/Documentation/git-blame.txt
b/Documentation/git-blame.txt
index b14e7940778da2295f1b61ab4096c3ba29b908f9..5dd8e36bbddad0a49af17196c43fc297b04285dc 100644
(file)
--- 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
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,60 foo
+ git blame -L 40,+21 foo
Also you can use regular expression to specify the line range.
Also you can use regular expression to specify the line range.