Commit bc26f7690a (clone: make it possible to specify --tags, 2025-02-06) added a new paragraph in the middle of this list item. By adding an empty line rather than using a list continuation, we broke the list continuation, with the new paragraph ending up funnily indented. Restore the chain of list continuations. Signed-off-by: Martin Ågren <martin.agren@xxxxxxxxx> --- Based immediately on top of bc26f7690a. Could equally well be queued onto some later point, modifying git-clone.adoc instead of .txt. Documentation/git-clone.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt index 8d0476f6dc..ebfb608885 100644 --- a/Documentation/git-clone.txt +++ b/Documentation/git-clone.txt @@ -279,9 +279,9 @@ corresponding `--mirror` and `--no-tags` options instead. `remote.<remote>.tagOpt=--no-tags` configuration. This ensures that future `git pull` and `git fetch` won't follow any tags. Subsequent explicit tag fetches will still work (see linkgit:git-fetch[1]). - - By default, tags are cloned and passing `--tags` is thus typically a - no-op, unless it cancels out a previous `--no-tags`. ++ +By default, tags are cloned and passing `--tags` is thus typically a +no-op, unless it cancels out a previous `--no-tags`. + Can be used in conjunction with `--single-branch` to clone and maintain a branch with no references other than a single cloned -- 2.49.0.rc1.472.g01f2b84529
