diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2007-01-17 23:27:45 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2007-01-17 23:27:45 +0000 |
| commit | e58607f49ae156d2e441edd280f99219614f52a8 (patch) | |
| tree | fb4e77e0217b020294a5e6fb2f9726cd94d86680 /git-blame.txt | |
| parent | 4f9a60570b88fc1b9076ae2f5cfecf43bce0c87c (diff) | |
| download | git-htmldocs-e58607f49ae156d2e441edd280f99219614f52a8.tar.gz | |
Autogenerated HTML docs for v1.5.0-rc1-gde38
Diffstat (limited to 'git-blame.txt')
| -rw-r--r-- | git-blame.txt | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/git-blame.txt b/git-blame.txt index b14e79407..5dd8e36bb 100644 --- a/git-blame.txt +++ b/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. |