development/git
development/git
1
0
Fork 0
mirror of https://github.com/git/git synced 2024-08-24 10:15:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Documentation: move blame examples

Browse source 
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>
This commit is contained in:
Junio C Hamano 2006-11-09 10:44:56 -08:00
parent 6a96b32d3b
commit 18d5453ed3
1 changed files with 7 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
Documentation/git-blame.txt
View file

@ -41,10 +41,7 @@ OPTIONS
Use the same output mode as gitlink:git-annotate[1] (Default: off).
-L n,m::
Annotate only the specified line range (lines count from
1). The range can be specified with a regexp. For
example, `-L '/^sub esc_html /,/^}$/'` limits the
annotation only to the body of `esc_html` subroutine.
Annotate only the specified line range (lines count from 1).
-l, --long::
Show long rev (Default: off).
@ -125,6 +122,12 @@ ll. 40-60 for file `foo`, you can use `-L` option like this:
git blame -L 40,60 foo
Also you can use regular expression to specify the line range.
git blame -L '/^sub hello {/,/^}$/' foo
would limit the annotation to the body of `hello` subroutine.
When you are not interested in changes older than the version
v2.6.18, or changes older than 3 weeks, you can use revision
range specifiers similar to `git-rev-list`: