{"thread":{"id":"61425","subject":"[PATCH] Documentation: Mention that refspecs are explained elsewhere","startedAt":"2024-05-06T18:23:26Z","lastAt":"2024-05-06T19:12:13Z","messageCount":2,"participants":["Øystein Walle","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"494174","messageId":"20240506182317.13477-1-oystwa@gmail.com","threadId":"61425","inReplyTo":null,"subject":"[PATCH] Documentation: Mention that refspecs are explained elsewhere","fromName":"Øystein Walle","fromEmail":"oystwa@gmail.com","sentAt":"2024-05-06T18:23:17Z","receivedAt":"2024-05-06T18:23:26Z","isPatch":true,"sender":{"key":"oystwa@gmail.com","avatar":"https://avatars.githubusercontent.com/u/794585?v=4"},"body":"The syntax for refspecs are explained in more detail in documention for\ngit-fetch and git-push. Give a hint to the user too look there more fore\ninformation\n\nSigned-off-by: Øystein Walle <oystwa@gmail.com>\n---\n Documentation/glossary-content.txt | 3 ++-\n 1 file changed, 2 insertions(+), 1 deletion(-)\n\ndiff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt\nindex d71b199955..1272809e13 100644\n--- a/Documentation/glossary-content.txt\n+++ b/Documentation/glossary-content.txt\n@@ -576,7 +576,8 @@ The most notable example is `HEAD`.\n [[def_refspec]]refspec::\n \tA \"refspec\" is used by <<def_fetch,fetch>> and\n \t<<def_push,push>> to describe the mapping between remote\n-\t<<def_ref,ref>> and local ref.\n+\t<<def_ref,ref>> and local ref. See linkgit:git-fetch[1] or\n+\tlinkgit:git-push[1] for details.\n \n [[def_remote]]remote repository::\n \tA <<def_repository,repository>> which is used to track the same\n-- \n2.40.1\n\n"},{"id":"494182","messageId":"xmqqo79iycu0.fsf@gitster.g","threadId":"61425","inReplyTo":"20240506182317.13477-1-oystwa@gmail.com","subject":"Re: [PATCH] Documentation: Mention that refspecs are explained elsewhere","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-05-06T19:12:07Z","receivedAt":"2024-05-06T19:12:13Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Øystein Walle <oystwa@gmail.com> writes:\n\n> The syntax for refspecs are explained in more detail in documention for\n> git-fetch and git-push. Give a hint to the user too look there more fore\n> information\n\nSounds sensible.  It is a bit unsatisfying that we cannot make the\nglossary entry the single source of the authoritative truth, but the\nrefspec syntax needs to be slightly different between fetches and\npushes (hence Documention/git-push.txt does not include the same\nDocumentation/pull-fetch-param.txt like Documentation/git-fetch.txt\ndoes), so this is probably the best we could do.\n\n> Signed-off-by: Øystein Walle <oystwa@gmail.com>\n> ---\n>  Documentation/glossary-content.txt | 3 ++-\n>  1 file changed, 2 insertions(+), 1 deletion(-)\n>\n> diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt\n> index d71b199955..1272809e13 100644\n> --- a/Documentation/glossary-content.txt\n> +++ b/Documentation/glossary-content.txt\n> @@ -576,7 +576,8 @@ The most notable example is `HEAD`.\n>  [[def_refspec]]refspec::\n>  \tA \"refspec\" is used by <<def_fetch,fetch>> and\n>  \t<<def_push,push>> to describe the mapping between remote\n> -\t<<def_ref,ref>> and local ref.\n> +\t<<def_ref,ref>> and local ref. See linkgit:git-fetch[1] or\n> +\tlinkgit:git-push[1] for details.\n\nWill queue.  Thanks.\n"}]}