blame-options.txt: also mention 'funcname' in '-L' description
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>
Philippe Blain committed
Nov 1, 2020 at 17:28 UTC
a4514a46d9c85278ae4a350442dd4a160ff1f3cf
2 files changed
+5
-4
Documentation/blame-options.txt
+3
-2
@@ -11,8 +11,9 @@
11
12
-L <start>,<end>::
13
-L :<funcname>::
14
- Annotate only the given line range. May be specified multiple times.
15
- Overlapping ranges are allowed.
14
+ Annotate only the line range given by '<start>,<end>',
15
+ or by the function name regex '<funcname>'.
16
+ May be specified multiple times. Overlapping ranges are allowed.
17
+
18
'<start>' and '<end>' are optional. `-L <start>` or `-L <start>,` spans from
19
'<start>' to end of file. `-L ,<end>` spans from start of file to '<end>'.
Documentation/line-range-options.txt
+2
-2
@@ -1,8 +1,8 @@
1
-L<start>,<end>:<file>::
2
-L:<funcname>:<file>::
3
4
- Trace the evolution of the line range given by '<start>,<end>'
5
- (or the function name regex '<funcname>') within the '<file>'. You may
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