All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/glossary: fix double word
Date: Mon, 22 Jul 2024 09:49:38 +0200	[thread overview]
Message-ID: <Zp4PElBU1kLwLpGY@tanuki> (raw)
In-Reply-To: <20240717105432.2801097-2-martin.agren@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]

On Wed, Jul 17, 2024 at 12:54:29PM +0200, Martin Ågren wrote:
> Remove a spurious "that".
> 
> Signed-off-by: Martin Ågren <martin.agren@gmail.com>

This looks obviously correct to me. Thanks!

Patrick

> ---
>  This buglet was introduced in 74b50a5881 (Documentation/glossary: define
>  root refs as refs, 2024-05-15) as part of ps/pseudo-ref-terminology.
> 
>  Documentation/glossary-content.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
> index 30b394ab47..42afe04869 100644
> --- a/Documentation/glossary-content.txt
> +++ b/Documentation/glossary-content.txt
> @@ -550,7 +550,7 @@ The following pseudorefs are known to Git:
>  	to the result.
>  
>  [[def_ref]]ref::
> -	A name that that points to an <<def_object_name,object name>> or
> +	A name that points to an <<def_object_name,object name>> or
>  	another ref (the latter is called a <<def_symref,symbolic ref>>).
>  	For convenience, a ref can sometimes be abbreviated when used
>  	as an argument to a Git command; see linkgit:gitrevisions[7]
> -- 
> 2.46.0.rc0.321.g44c27ab58a
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-07-22  7:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 10:54 [PATCH] Documentation/glossary: fix double word Martin Ågren
2024-07-22  7:49 ` Patrick Steinhardt [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=Zp4PElBU1kLwLpGY@tanuki \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=martin.agren@gmail.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.