Documentation: move blame examples
This moves the example to specify a line range with regexps to a later part of the manual page that has similar examples. Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Nov 9, 2006 at 10:44 UTC
18d5453ed36331b3f4123afae6c1c6bb4ef4d0a5
1 file changed
+7
-4
Documentation/git-blame.txt
+7
-4
@@ -41,10 +41,7 @@ OPTIONS
41
Use the same output mode as gitlink:git-annotate[1] (Default: off).
42
43
-L n,m::
44
- Annotate only the specified line range (lines count from
45
- 1). The range can be specified with a regexp. For
46
- example, `-L '/^sub esc_html /,/^}$/'` limits the
47
- annotation only to the body of `esc_html` subroutine.
44
+ Annotate only the specified line range (lines count from 1).
45
46
-l, --long::
47
Show long rev (Default: off).
@@ -125,6 +122,12 @@ ll. 40-60 for file `foo`, you can use `-L` option like this:
122
123
git blame -L 40,60 foo
124
125
+Also you can use regular expression to specify the line range.
126
+
127
+ git blame -L '/^sub hello {/,/^}$/' foo
128
+
129
+would limit the annotation to the body of `hello` subroutine.
130
+
131
When you are not interested in changes older than the version
132
v2.6.18, or changes older than 3 weeks, you can use revision
133
range specifiers similar to `git-rev-list`: