undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation: change -L:<regex> to -L:<funcname>

Browse Source 
The old wording was somehow implying that <start> and <end> were not
regular expressions. Also, the common case is to use a plain function
name here so <funcname> makes sense (the fact that it is a regular
expression is documented in line-range-format.txt).

Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Matthieu Moy 2015-04-20 14:09:06 +02:00 committed by Junio C Hamano
parent 52735a6892
commit d349e0ee60
4 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/blame-options.txt
View File

@ -10,7 +10,7 @@
Include additional statistics at the end of blame output. Include additional statistics at the end of blame output.
-L <start>,<end>:: -L <start>,<end>::
-L :<regex>:: -L :<funcname>::
Annotate only the given line range. May be specified multiple times. Annotate only the given line range. May be specified multiple times.
Overlapping ranges are allowed. Overlapping ranges are allowed.
+ +

4
Documentation/git-log.txt
View File

@ -62,9 +62,9 @@ produced by `--stat`, etc.
output by allowing them to allocate space in advance. output by allowing them to allocate space in advance.
-L <start>,<end>:<file>:: -L <start>,<end>:<file>::
-L :<regex>:<file>:: -L :<funcname>:<file>::
Trace the evolution of the line range given by "<start>,<end>" Trace the evolution of the line range given by "<start>,<end>"
(or the funcname regex <regex>) within the <file>. You may (or the function name regex <funcname>) within the <file>. You may
not give any pathspec limiters. This is currently limited to not give any pathspec limiters. This is currently limited to
a walk starting from a single revision, i.e., you may only a walk starting from a single revision, i.e., you may only
give zero or one positive revision arguments. give zero or one positive revision arguments.

4
Documentation/gitk.txt
View File

@ -99,10 +99,10 @@ linkgit:git-rev-list[1] for a complete list.
detailed explanation.) detailed explanation.)
-L<start>,<end>:<file>:: -L<start>,<end>:<file>::
-L:<regex>:<file>:: -L:<funcname>:<file>::
Trace the evolution of the line range given by "<start>,<end>" Trace the evolution of the line range given by "<start>,<end>"
(or the funcname regex <regex>) within the <file>. You may (or the function name regex <funcname>) within the <file>. You may
not give any pathspec limiters. This is currently limited to not give any pathspec limiters. This is currently limited to
a walk starting from a single revision, i.e., you may only a walk starting from a single revision, i.e., you may only
give zero or one positive revision arguments. give zero or one positive revision arguments.

11
Documentation/line-range-format.txt
View File

@ -22,8 +22,9 @@ This is only valid for <end> and will specify a number
of lines before or after the line given by <start>. of lines before or after the line given by <start>.
+ +
If ``:<regex>'' is given in place of <start> and <end>, it denotes the range If ``:<funcname>'' is given in place of <start> and <end>, it is a
from the first funcname line that matches <regex>, up to the next regular expression that denotes the range from the first funcname line
funcname line. ``:<regex>'' searches from the end of the previous `-L` range, that matches <funcname>, up to the next funcname line. ``:<funcname>''
if any, otherwise from the start of file. searches from the end of the previous `-L` range, if any, otherwise
``^:<regex>'' searches from the start of file. from the start of file. ``^:<funcname>'' searches from the start of
file.