git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] git-clone doc: fix indentation
@ 2025-03-10 11:07 Martin Ågren
  2025-03-10 16:55 ` Junio C Hamano
  0 siblings, 1 reply; 2+ messages in thread
From: Martin Ågren @ 2025-03-10 11:07 UTC (permalink / raw)
  To: git; +Cc: Martin Ågren, Toon Claes

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@gmail.com>
---
 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


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] git-clone doc: fix indentation
  2025-03-10 11:07 [PATCH] git-clone doc: fix indentation Martin Ågren
@ 2025-03-10 16:55 ` Junio C Hamano
  0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2025-03-10 16:55 UTC (permalink / raw)
  To: Martin Ågren; +Cc: git, Toon Claes

Martin Ågren <martin.agren@gmail.com> writes:

> 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@gmail.com>
> ---
>  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

Thanks.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-03-10 16:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-10 11:07 [PATCH] git-clone doc: fix indentation Martin Ågren
2025-03-10 16:55 ` Junio C Hamano

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).