All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Brett A C Sheffield <bacs@librecast.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitremote-helpers.adoc: fix formatting
Date: Wed, 02 Jul 2025 11:59:03 -0700	[thread overview]
Message-ID: <xmqqecuyctc8.fsf@gitster.g> (raw)
In-Reply-To: <20250702161951.22908-2-bacs@librecast.net> (Brett A. C. Sheffield's message of "Wed, 2 Jul 2025 18:19:52 +0200")

Brett A C Sheffield <bacs@librecast.net> writes:

> From: Brett A C Sheffield (Librecast) <bacs@librecast.net>
>
> Add missing colon to fix formatting.
>
> Signed-off-by: Brett A C Sheffield <bacs@librecast.net>
> ---
>  Documentation/gitremote-helpers.adoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/gitremote-helpers.adoc b/Documentation/gitremote-helpers.adoc
> index d0be008e5e..39cdece16e 100644
> --- a/Documentation/gitremote-helpers.adoc
> +++ b/Documentation/gitremote-helpers.adoc
> @@ -498,7 +498,7 @@ set by Git if the remote helper has the 'option' capability.
>  	ask for the tag specifically.  Some helpers may be able to
>  	use this option to avoid a second network connection.
>  
> -'option dry-run' {'true'|'false'}:
> +'option dry-run' {'true'|'false'}::
>  	If true, pretend the operation completed successfully,
>  	but don't actually change any repository data.  For most
>  	helpers this only applies to the 'push', if supported.
>
> base-commit: 16bd9f20a403117f2e0d9bcda6c6e621d3763e77

Wow, that is an old typo that dates back a bit more than 10 years
;-)

Thanks for spotting and fixing it.
Will queue.

      reply	other threads:[~2025-07-02 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 16:19 [PATCH] gitremote-helpers.adoc: fix formatting Brett A C Sheffield
2025-07-02 18:59 ` 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=xmqqecuyctc8.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=bacs@librecast.net \
    --cc=git@vger.kernel.org \
    /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.