Documentation/gitk: document -L option
The -L option is the same as for git-log, so the entire block is just copied from git-log.txt. However, until the parser is fixed we add a caveat that gitk only understands the stuck form. Signed-off-by: Thomas Rast <tr@thomasrast.ch> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Thomas Rast committed
Nov 16, 2013 at 18:37 UTC
0c1cddd01543feb101c0d95180e27ab840b280b9
1 file changed
+16
Documentation/gitk.txt
+16
@@ -98,6 +98,22 @@ linkgit:git-rev-list[1] for a complete list.
98
(See "History simplification" in linkgit:git-log[1] for a more
99
detailed explanation.)
100
101
+-L<start>,<end>:<file>::
102
+-L:<regex>:<file>::
103
+
104
+ Trace the evolution of the line range given by "<start>,<end>"
105
+ (or the funcname regex <regex>) within the <file>. You may
106
+ not give any pathspec limiters. This is currently limited to
107
+ a walk starting from a single revision, i.e., you may only
108
+ give zero or one positive revision arguments.
109
+ You can specify this option more than once.
110
++
111
+*Note:* gitk (unlike linkgit:git-log[1]) currently only understands
112
+this option if you specify it "glued together" with its argument. Do
113
+*not* put a space after `-L`.
114
++
115
+include::line-range-format.txt[]
116
+
117
<revision range>::
118
119
Limit the revisions to show. This can be either a single revision