mirror of
https://github.com/git/git
synced 2024-08-24 10:15:51 +00:00
![Philippe Blain](/assets/img/avatar_default.png)
Make it clearer that a function can be blamed by feeding `git blame` '-L :<funcname>' by mentioning it at the beginnning of the description of the '-L' option. Also, in 'line-range-options.txt', which is used for git-log(1) and gitk(1), do not parenthesize the mention of the ':<funcname>' mode, to place it on equal footing with the '<start>,<end>' mode. Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
16 lines
761 B
Plaintext
16 lines
761 B
Plaintext
-L<start>,<end>:<file>::
|
|
-L:<funcname>:<file>::
|
|
|
|
Trace the evolution of the line range given by '<start>,<end>',
|
|
or by the function name regex '<funcname>', within the '<file>'. You may
|
|
not give any pathspec limiters. This is currently limited to
|
|
a walk starting from a single revision, i.e., you may only
|
|
give zero or one positive revision arguments, and
|
|
'<start>' and '<end>' (or '<funcname>') must exist in the starting revision.
|
|
You can specify this option more than once. Implies `--patch`.
|
|
Patch output can be suppressed using `--no-patch`, but other diff formats
|
|
(namely `--raw`, `--numstat`, `--shortstat`, `--dirstat`, `--summary`,
|
|
`--name-only`, `--name-status`, `--check`) are not currently implemented.
|
|
+
|
|
include::line-range-format.txt[]
|