public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: kristofferhaugsbakk@fastmail•com
Cc: git@vger•kernel.org,  Kristoffer Haugsbakk <code@khaugsbakk•name>,
	Patrick Steinhardt <ps@pks•im>
Subject: Re: [PATCH] doc: maintenance: fix linkgit syntax
Date: Mon, 09 Jun 2025 11:34:25 -0700	[thread overview]
Message-ID: <xmqqsek8rcge.fsf@gitster.g> (raw)
In-Reply-To: <567195e5577c6c32b46f784a797fbf366873a0f3.1749484736.git.code@khaugsbakk.name> (kristofferhaugsbakk@fastmail.com's message of "Mon, 9 Jun 2025 17:59:42 +0200")

kristofferhaugsbakk@fastmail•com writes:

> From: Kristoffer Haugsbakk <code@khaugsbakk•name>
>
> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk•name>
> ---
>
> Notes (series):
>     I get no more hits with this search
>     
>         cd Documentation
>         git grep --no-index ':git-.*[123456789]' -- '*.html'

Thanks for being thorough.

The patch looks good.  Will queue.


>  Documentation/git-maintenance.adoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-maintenance.adoc b/Documentation/git-maintenance.adoc
> index 931f3e02e85..540b5cf68b0 100644
> --- a/Documentation/git-maintenance.adoc
> +++ b/Documentation/git-maintenance.adoc
> @@ -172,7 +172,7 @@ rerere-gc::
>  
>  worktree-prune::
>  	The `worktree-prune` task deletes stale or broken worktrees. See
> -	linkit:git-worktree[1] for more information.
> +	linkgit:git-worktree[1] for more information.
>  
>  OPTIONS
>  -------
>
> base-commit: 8db3019401f8093fb895f581be641fe7e05aa755

      reply	other threads:[~2025-06-09 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 15:59 [PATCH] doc: maintenance: fix linkgit syntax kristofferhaugsbakk
2025-06-09 18:34 ` 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=xmqqsek8rcge.fsf@gitster.g \
    --to=gitster@pobox$(echo .)com \
    --cc=code@khaugsbakk$(echo .)name \
    --cc=git@vger$(echo .)kernel.org \
    --cc=kristofferhaugsbakk@fastmail$(echo .)com \
    --cc=ps@pks$(echo .)im \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox