{"thread":{"id":"63087","subject":"[PATCH] git-clone doc: fix indentation","startedAt":"2025-03-10T11:08:03Z","lastAt":"2025-03-10T16:55:31Z","messageCount":2,"participants":["Martin Ågren","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"513891","messageId":"20250310110758.601206-1-martin.agren@gmail.com","threadId":"63087","inReplyTo":null,"subject":"[PATCH] git-clone doc: fix indentation","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2025-03-10T11:07:56Z","receivedAt":"2025-03-10T11:08:03Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"Commit bc26f7690a (clone: make it possible to specify --tags,\n2025-02-06) added a new paragraph in the middle of this list item. By\nadding an empty line rather than using a list continuation, we broke the\nlist continuation, with the new paragraph ending up funnily indented.\n\nRestore the chain of list continuations.\n\nSigned-off-by: Martin Ågren <martin.agren@gmail.com>\n---\n Based immediately on top of bc26f7690a. Could equally well be queued\n onto some later point, modifying git-clone.adoc instead of .txt. \n\n Documentation/git-clone.txt | 6 +++---\n 1 file changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt\nindex 8d0476f6dc..ebfb608885 100644\n--- a/Documentation/git-clone.txt\n+++ b/Documentation/git-clone.txt\n@@ -279,9 +279,9 @@ corresponding `--mirror` and `--no-tags` options instead.\n \t`remote.<remote>.tagOpt=--no-tags` configuration. This ensures that\n \tfuture `git pull` and `git fetch` won't follow any tags. Subsequent\n \texplicit tag fetches will still work (see linkgit:git-fetch[1]).\n-\n-\tBy default, tags are cloned and passing `--tags` is thus typically a\n-\tno-op, unless it cancels out a previous `--no-tags`.\n++\n+By default, tags are cloned and passing `--tags` is thus typically a\n+no-op, unless it cancels out a previous `--no-tags`.\n +\n Can be used in conjunction with `--single-branch` to clone and\n maintain a branch with no references other than a single cloned\n-- \n2.49.0.rc1.472.g01f2b84529\n\n"},{"id":"513923","messageId":"xmqq8qpc9668.fsf@gitster.g","threadId":"63087","inReplyTo":"20250310110758.601206-1-martin.agren@gmail.com","subject":"Re: [PATCH] git-clone doc: fix indentation","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-03-10T16:55:27Z","receivedAt":"2025-03-10T16:55:31Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Martin Ågren <martin.agren@gmail.com> writes:\n\n> Commit bc26f7690a (clone: make it possible to specify --tags,\n> 2025-02-06) added a new paragraph in the middle of this list item. By\n> adding an empty line rather than using a list continuation, we broke the\n> list continuation, with the new paragraph ending up funnily indented.\n>\n> Restore the chain of list continuations.\n>\n> Signed-off-by: Martin Ågren <martin.agren@gmail.com>\n> ---\n>  Based immediately on top of bc26f7690a. Could equally well be queued\n>  onto some later point, modifying git-clone.adoc instead of .txt. \n>\n>  Documentation/git-clone.txt | 6 +++---\n>  1 file changed, 3 insertions(+), 3 deletions(-)\n>\n> diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt\n> index 8d0476f6dc..ebfb608885 100644\n> --- a/Documentation/git-clone.txt\n> +++ b/Documentation/git-clone.txt\n> @@ -279,9 +279,9 @@ corresponding `--mirror` and `--no-tags` options instead.\n>  \t`remote.<remote>.tagOpt=--no-tags` configuration. This ensures that\n>  \tfuture `git pull` and `git fetch` won't follow any tags. Subsequent\n>  \texplicit tag fetches will still work (see linkgit:git-fetch[1]).\n> -\n> -\tBy default, tags are cloned and passing `--tags` is thus typically a\n> -\tno-op, unless it cancels out a previous `--no-tags`.\n> ++\n> +By default, tags are cloned and passing `--tags` is thus typically a\n> +no-op, unless it cancels out a previous `--no-tags`.\n>  +\n>  Can be used in conjunction with `--single-branch` to clone and\n>  maintain a branch with no references other than a single cloned\n\nThanks.\n"}]}