summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Rast <tr@thomasrast.ch>2013-11-16 18:37:57 +0100
committerJunio C Hamano <gitster@pobox.com>2014-01-21 13:41:30 -0800
commit0c1cddd01543feb101c0d95180e27ab840b280b9 (patch)
tree0534da3ef78cde271152aee4868999e1b8d27c29
parentd9bb4be53bc5185244b4be9860562a012803bacb (diff)
downloadgit-tr/gitk-doc-range-trace.tar.gz
Documentation/gitk: document -L optiontr/gitk-doc-range-trace
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>
-rw-r--r--Documentation/gitk.txt16
1 files changed, 16 insertions, 0 deletions
diff --git a/Documentation/gitk.txt b/Documentation/gitk.txt
index d44e14c138..1e9e38ae40 100644
--- a/Documentation/gitk.txt
+++ b/Documentation/gitk.txt
@@ -98,6 +98,22 @@ linkgit:git-rev-list[1] for a complete list.
(See "History simplification" in linkgit:git-log[1] for a more
detailed explanation.)
+-L<start>,<end>:<file>::
+-L:<regex>:<file>::
+
+ Trace the evolution of the line range given by "<start>,<end>"
+ (or the funcname regex <regex>) 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.
+ You can specify this option more than once.
++
+*Note:* gitk (unlike linkgit:git-log[1]) currently only understands
+this option if you specify it "glued together" with its argument. Do
+*not* put a space after `-L`.
++
+include::line-range-format.txt[]
+
<revision range>::
Limit the revisions to show. This can be either a single revision