From 18d5453ed36331b3f4123afae6c1c6bb4ef4d0a5 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Thu, 9 Nov 2006 10:44:56 -0800 Subject: [PATCH] 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 --- Documentation/git-blame.txt | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt index ff54d29d7..bdfc66692 100644 --- a/Documentation/git-blame.txt +++ b/Documentation/git-blame.txt @@ -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`: -- 2.30.2