From 18f98295e46464b45b0246bcb8efcb5e0b98da13 Mon Sep 17 00:00:00 2001 From: Elijah Newren Date: Sat, 1 Feb 2020 09:43:29 -0800 Subject: [PATCH] git-filter-repo.txt: fix nested bullets to render correctly Signed-off-by: Elijah Newren --- Documentation/git-filter-repo.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-filter-repo.txt b/Documentation/git-filter-repo.txt index 6fb571d..1ef5e5b 100644 --- a/Documentation/git-filter-repo.txt +++ b/Documentation/git-filter-repo.txt @@ -1049,9 +1049,9 @@ the user when it detects an issue: * When rewriting commit hashes in commit messages, there are a variety of cases when the hash will not be updated (whenever this happens, a note is written to `.git/filter-repo/suboptimal-issues`): - * if a commit hash does not correspond to a commit in the old repo - * if a commit hash corresponds to a commit that gets pruned - * if an abbreviated hash is not unique + ** if a commit hash does not correspond to a commit in the old repo + ** if a commit hash corresponds to a commit that gets pruned + ** if an abbreviated hash is not unique * Pruning of empty commits can cause a merge commit to lose an entire ancestry line and become a non-merge. If the merge commit had no