| 1 | `-L<start>,<end>:<file>`:: |
| 2 | `-L:<funcname>:<file>`:: |
| 3 | |
| 4 | Trace the evolution of the line range given by `<start>,<end>`, |
| 5 | or by the function name regex _<funcname>_, within the _<file>_. You may |
| 6 | not give any pathspec limiters. This is currently limited to |
| 7 | a walk starting from a single revision, i.e., you may only |
| 8 | give zero or one positive revision arguments, and |
| 9 | _<start>_ and _<end>_ (or _<funcname>_) must exist in the starting revision. |
| 10 | You can specify this option more than once. Implies `--patch`. |
| 11 | Patch output can be suppressed using `--no-patch`. |
| 12 | The following non-patch diff formats are supported: `--raw`, |
| 13 | `--name-only`, `--name-status`, `--summary`, `--check`, |
| 14 | `--stat`, `--numstat`, and `--shortstat`. |
| 15 | The stat formats count only lines within the tracked range. |
| 16 | `--dirstat` is not supported |
| 17 | with `-L`: it summarizes change as each directory's share of |
| 18 | the total churn, not as counts for the tracked lines. Use |
| 19 | `--numstat` for exact per-file counts within the range. |
| 20 | + |
| 21 | Patch formatting options such as `--word-diff`, `--color-moved`, |
| 22 | `--no-prefix`, and whitespace options (`-w`, `-b`) are supported, |
| 23 | as are pickaxe options (`-S`, `-G`) and `--diff-filter`. `-G` is |
| 24 | scoped to the tracked range; `-S` is still evaluated over the whole |
| 25 | file, so an `-S` query may select a commit for a change outside the |
| 26 | range. |
| 27 | + |
| 28 | include::line-range-format.adoc[] |