99--------
1010[verse]
1111'git blame' [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-e] [-p] [-w] [--incremental]
12- [-L n,m | -L :fn ] [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>]
12+ [-L <range> ] [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>]
1313 [--abbrev=<n>] [<rev> | --contents <file> | --reverse <rev>] [--] <file>
1414
1515DESCRIPTION
@@ -18,7 +18,8 @@ DESCRIPTION
1818Annotates each line in the given file with information from the revision which
1919last modified the line. Optionally, start annotating from the given revision.
2020
21- The command can also limit the range of lines annotated.
21+ When specified one or more times, `-L` restricts annotation to the requested
22+ lines.
2223
2324The origin of lines is automatically followed across whole-file
2425renames (currently there is no option to turn the rename-following
@@ -130,7 +131,10 @@ SPECIFYING RANGES
130131
131132Unlike 'git blame' and 'git annotate' in older versions of git, the extent
132133of the annotation can be limited to both line ranges and revision
133- ranges. When you are interested in finding the origin for
134+ ranges. The `-L` option, which limits annotation to a range of lines, may be
135+ specified multiple times.
136+
137+ When you are interested in finding the origin for
134138lines 40-60 for file `foo`, you can use the `-L` option like so
135139(they mean the same thing -- both ask for 21 lines starting at
136140line 40):
0 commit comments