summaryrefslogtreecommitdiffstats
path: root/git-filter-branch.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2019-12-01 14:58:27 -0800
committerJunio C Hamano <gitster@pobox.com>2019-12-01 14:58:27 -0800
commit8ef91f31f6606a0370b18943c3b0f089e04873f9 (patch)
tree2bf27a3779a34fa4bf69dfc02e1fe1be848ea0d2 /git-filter-branch.html
parent8ac8a3d8dd001611b77776fa19ef37c2c87cd987 (diff)
downloadgit-htmldocs-8ef91f31f6606a0370b18943c3b0f089e04873f9.tar.gz
Autogenerated HTML docs for v2.24.0-308-g228f5
Diffstat (limited to 'git-filter-branch.html')
-rw-r--r--git-filter-branch.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/git-filter-branch.html b/git-filter-branch.html
index 15cdc133a..155ef66bc 100644
--- a/git-filter-branch.html
+++ b/git-filter-branch.html
@@ -1377,7 +1377,7 @@ repo-filter</em> also provides
<a href="https://github.com/newren/git-filter-repo/blob/master/contrib/filter-repo-demos/filter-lamely">filter-lamely</a>,
a drop-in git-filter-branch replacement (with a few caveats). While
filter-lamely suffers from all the same safety issues as
-git-filter-branch, it at least ameloriates the performance issues a
+git-filter-branch, it at least ameliorates the performance issues a
little.</p></div>
</div>
</div>
@@ -1549,7 +1549,7 @@ just pruning commits that became empty due to filtering rules.
</li>
<li>
<p>
-If --prune empty is specified, sometimes empty commits are missed
+If --prune-empty is specified, sometimes empty commits are missed
and left around anyway (a somewhat rare bug, but it happens&#8230;)
</p>
</li>
@@ -1617,7 +1617,7 @@ where it doesn&#8217;t work, as noted above.
<div id="footer">
<div id="footer-text">
Last updated
- 2019-09-30 14:04:22 JST
+ 2019-12-01 14:55:34 PST
</div>
</div>
</body>