summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2020-02-12 12:41:37 -0800
committerJunio C Hamano <gitster@pobox.com>2020-02-12 12:41:37 -0800
commit3d2471ba855e536489710114b609482b9f781a24 (patch)
tree688decb14293f8585a8b05d397b4690ba17ed91a
parentb2099ebb123af2b299c8125b7a839df44faec68a (diff)
parente469afe158a9c8a4b2aa9a753f80d034a8fc7f05 (diff)
downloadgit-3d2471ba855e536489710114b609482b9f781a24.tar.gz
Merge branch 'ma/filter-branch-doc-caret'
Doc mark-up updates. * ma/filter-branch-doc-caret: git-filter-branch.txt: wrap "maths" notation in backticks
-rw-r--r--Documentation/git-filter-branch.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt
index a530fef7e5..40ba4aa3e6 100644
--- a/Documentation/git-filter-branch.txt
+++ b/Documentation/git-filter-branch.txt
@@ -467,9 +467,9 @@ impossible for a backward-compatible implementation to ever be fast:
* In editing files, git-filter-branch by design checks out each and
every commit as it existed in the original repo. If your repo has
- 10\^5 files and 10\^5 commits, but each commit only modifies 5
- files, then git-filter-branch will make you do 10\^10 modifications,
- despite only having (at most) 5*10^5 unique blobs.
+ `10^5` files and `10^5` commits, but each commit only modifies five
+ files, then git-filter-branch will make you do `10^10` modifications,
+ despite only having (at most) `5*10^5` unique blobs.
* If you try and cheat and try to make git-filter-branch only work on
files modified in a commit, then two things happen