[PATCH] git-filter-branch.txt: use {caret} for ^
- From
- Martin Ågren <martin.agren@gmail.com>
- Date
- Feb 2, 2020, 19:33 UTC
- Message-ID
- <20200202193319.1966-1-martin.agren@gmail.com>
In this paragraph, we have a few instances of the '^' character, which we give as "\^". This renders well with AsciiDoc ("^"), but Asciidoctor renders it literally as "\^". Dropping the backslashes renders fine with Asciidoctor, but not AsciiDoc... Let's use "{caret}" instead, to avoid these escaping problems.
Signed-off-by: Martin Ågren <martin.agren@gmail.com> --- Documentation/git-filter-branch.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt index a530fef7e5..9e58d34c6a 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{caret}5 files and 10{caret}5 commits, but each commit only modifies 5 + files, then git-filter-branch will make you do 10{caret}10 modifications, + despite only having (at most) 5*10{caret}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
-- 2.25.0