Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <>
To: "Øystein Walle" <>
Subject: Re: [PATCH] Documentation: Mention that refspecs are explained elsewhere
Date: Mon, 06 May 2024 12:12:07 -0700	[thread overview]
Message-ID: <xmqqo79iycu0.fsf@gitster.g> (raw)
In-Reply-To: <> ("Øystein Walle"'s message of "Mon, 6 May 2024 20:23:17 +0200")

Øystein Walle <> writes:

> The syntax for refspecs are explained in more detail in documention for
> git-fetch and git-push. Give a hint to the user too look there more fore
> information

Sounds sensible.  It is a bit unsatisfying that we cannot make the
glossary entry the single source of the authoritative truth, but the
refspec syntax needs to be slightly different between fetches and
pushes (hence Documention/git-push.txt does not include the same
Documentation/pull-fetch-param.txt like Documentation/git-fetch.txt
does), so this is probably the best we could do.

> Signed-off-by: Øystein Walle <>
> ---
>  Documentation/glossary-content.txt | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
> index d71b199955..1272809e13 100644
> --- a/Documentation/glossary-content.txt
> +++ b/Documentation/glossary-content.txt
> @@ -576,7 +576,8 @@ The most notable example is `HEAD`.
>  [[def_refspec]]refspec::
>  	A "refspec" is used by <<def_fetch,fetch>> and
>  	<<def_push,push>> to describe the mapping between remote
> -	<<def_ref,ref>> and local ref.
> +	<<def_ref,ref>> and local ref. See linkgit:git-fetch[1] or
> +	linkgit:git-push[1] for details.

Will queue.  Thanks.

      reply	other threads:[~2024-05-06 19:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 18:23 [PATCH] Documentation: Mention that refspecs are explained elsewhere Øystein Walle
2024-05-06 19:12 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqo79iycu0.fsf@gitster.g \ \ \ \

* 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 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 read-only IMAP folder(s) and NNTP newsgroup(s).