summaryrefslogtreecommitdiffstats
path: root/gitk.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2020-11-18 14:15:08 -0800
committerJunio C Hamano <gitster@pobox.com>2020-11-18 14:15:08 -0800
commitb7676d5ada0941ade7ac9acb8ce985686b62b2ab (patch)
tree11ddf24c8178241b09e082064ac45508a805f0e6 /gitk.html
parentee43d18844df1f78dad8b389cbb393b211073d17 (diff)
downloadgit-htmldocs-b7676d5ada0941ade7ac9acb8ce985686b62b2ab.tar.gz
Autogenerated HTML docs for v2.29.2-334-gfaefd
Diffstat (limited to 'gitk.html')
-rw-r--r--gitk.html39
1 files changed, 19 insertions, 20 deletions
diff --git a/gitk.html b/gitk.html
index 02189f5ce..8b06f190e 100644
--- a/gitk.html
+++ b/gitk.html
@@ -893,54 +893,53 @@ command-line parser.</p></div>
</dt>
<dd>
<p>
- Trace the evolution of the line range given by "&lt;start&gt;,&lt;end&gt;"
- (or the function name regex &lt;funcname&gt;) within the &lt;file&gt;. You may
+ Trace the evolution of the line range given by <em>&lt;start&gt;,&lt;end&gt;</em>,
+ or by the function name regex <em>&lt;funcname&gt;</em>, within the <em>&lt;file&gt;</em>. 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
- &lt;start&gt; and &lt;end&gt; (or &lt;funcname&gt;) must exist in the starting revision.
+ <em>&lt;start&gt;</em> and <em>&lt;end&gt;</em> (or <em>&lt;funcname&gt;</em>) must exist in the starting revision.
You can specify this option more than once. Implies <code>--patch</code>.
Patch output can be suppressed using <code>--no-patch</code>, but other diff formats
(namely <code>--raw</code>, <code>--numstat</code>, <code>--shortstat</code>, <code>--dirstat</code>, <code>--summary</code>,
<code>--name-only</code>, <code>--name-status</code>, <code>--check</code>) are not currently implemented.
</p>
-<div class="paragraph"><p><strong>Note:</strong> gitk (unlike <a href="git-log.html">git-log(1)</a>) currently only understands
-this option if you specify it "glued together" with its argument. Do
-<strong>not</strong> put a space after <code>-L</code>.</p></div>
-<div class="paragraph"><p>&lt;start&gt; and &lt;end&gt; can take one of these forms:</p></div>
+<div class="paragraph"><p><em>&lt;start&gt;</em> and <em>&lt;end&gt;</em> can take one of these forms:</p></div>
<div class="ulist"><ul>
<li>
<p>
number
</p>
-<div class="paragraph"><p>If &lt;start&gt; or &lt;end&gt; is a number, it specifies an
+<div class="paragraph"><p>If <em>&lt;start&gt;</em> or <em>&lt;end&gt;</em> is a number, it specifies an
absolute line number (lines count from 1).</p></div>
</li>
<li>
<p>
-/regex/
+<code>/regex/</code>
</p>
<div class="paragraph"><p>This form will use the first line matching the given
-POSIX regex. If &lt;start&gt; is a regex, it will search from the end of
+POSIX regex. If <em>&lt;start&gt;</em> is a regex, it will search from the end of
the previous <code>-L</code> range, if any, otherwise from the start of file.
-If &lt;start&gt; is &#8220;^/regex/&#8221;, it will search from the start of file.
-If &lt;end&gt; is a regex, it will search
-starting at the line given by &lt;start&gt;.</p></div>
+If <em>&lt;start&gt;</em> is <code>^/regex/</code>, it will search from the start of file.
+If <em>&lt;end&gt;</em> is a regex, it will search
+starting at the line given by <em>&lt;start&gt;</em>.</p></div>
</li>
<li>
<p>
+offset or -offset
</p>
-<div class="paragraph"><p>This is only valid for &lt;end&gt; and will specify a number
-of lines before or after the line given by &lt;start&gt;.</p></div>
+<div class="paragraph"><p>This is only valid for <em>&lt;end&gt;</em> and will specify a number
+of lines before or after the line given by <em>&lt;start&gt;</em>.</p></div>
</li>
</ul></div>
-<div class="paragraph"><p>If &#8220;:&lt;funcname&gt;&#8221; is given in place of &lt;start&gt; and &lt;end&gt;, it is a
+<div class="paragraph"><p>If <code>:&lt;funcname&gt;</code> is given in place of <em>&lt;start&gt;</em> and <em>&lt;end&gt;</em>, it is a
regular expression that denotes the range from the first funcname line
-that matches &lt;funcname&gt;, up to the next funcname line. &#8220;:&lt;funcname&gt;&#8221;
+that matches <em>&lt;funcname&gt;</em>, up to the next funcname line. <code>:&lt;funcname&gt;</code>
searches from the end of the previous <code>-L</code> range, if any, otherwise
-from the start of file. &#8220;^:&lt;funcname&gt;&#8221; searches from the start of
-file.</p></div>
+from the start of file. <code>^:&lt;funcname&gt;</code> searches from the start of
+file. The function names are determined in the same way as <code>git diff</code>
+works out patch hunk headers (see <em>Defining a custom hunk-header</em>
+in <a href="gitattributes.html">gitattributes(5)</a>).</p></div>
</dd>
<dt class="hdlist1">
&lt;revision range&gt;
@@ -1102,7 +1101,7 @@ of end users.</p></div>
<div id="footer">
<div id="footer-text">
Last updated
- 2020-03-10 08:03:13 PDT
+ 2020-11-18 14:12:24 PST
</div>
</div>
</body>