summaryrefslogtreecommitdiffstats
path: root/git-rebase.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2019-03-11 18:02:54 +0900
committerJunio C Hamano <gitster@pobox.com>2019-03-11 18:02:54 +0900
commitdecc7317e484bc31d0dfb457e70c9ad5a59fe7b1 (patch)
tree092cbff96396a7ea55a41cf8ddb2fe70e03ab722 /git-rebase.html
parent11f1537a82c84e620d742b3bc4256952defb28df (diff)
downloadgit-htmldocs-decc7317e484bc31d0dfb457e70c9ad5a59fe7b1.tar.gz
Autogenerated HTML docs for v2.21.0-155-ge902e
Diffstat (limited to 'git-rebase.html')
-rw-r--r--git-rebase.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/git-rebase.html b/git-rebase.html
index c5c13df37..a10d853cb 100644
--- a/git-rebase.html
+++ b/git-rebase.html
@@ -1404,7 +1404,7 @@ have the long commit hash prepended to the format.</p></div>
</p>
<div class="paragraph"><p>By default, or when <code>no-rebase-cousins</code> was specified, commits which do not
have <code>&lt;upstream&gt;</code> as direct ancestor will keep their original branch point,
-i.e. commits that would be excluded by gitlink:git-log[1]'s
+i.e. commits that would be excluded by <a href="git-log.html">git-log(1)</a>'s
<code>--ancestry-path</code> option will keep their original ancestry by default. If
the <code>rebase-cousins</code> mode is turned on, such commits are instead rebased
onto <code>&lt;upstream&gt;</code> (or <code>&lt;onto&gt;</code>, if specified).</p></div>
@@ -2452,7 +2452,7 @@ reorder commits tend to produce counterintuitive results. Use
<div id="footer">
<div id="footer-text">
Last updated
- 2019-02-19 15:22:22 PST
+ 2019-03-11 18:02:43 JST
</div>
</div>
</body>