From: Junio C Hamano <gitster@pobox.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: git@vger.kernel.org, Toon Claes <toon@iotcl.com>
Subject: Re: [PATCH] git-clone doc: fix indentation
Date: Mon, 10 Mar 2025 09:55:27 -0700 [thread overview]
Message-ID: <xmqq8qpc9668.fsf@gitster.g> (raw)
In-Reply-To: <20250310110758.601206-1-martin.agren@gmail.com> ("Martin Ågren"'s message of "Mon, 10 Mar 2025 12:07:56 +0100")
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.
prev parent reply other threads:[~2025-03-10 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 11:07 [PATCH] git-clone doc: fix indentation Martin Ågren
2025-03-10 16:55 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8qpc9668.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@gmail.com \
--cc=toon@iotcl.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.