git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Documentation: Mention that refspecs are explained elsewhere

From
Øystein Walle <oystwa@gmail.com>
Date
May 6, 2024, 18:23 UTC
Message-ID
<20240506182317.13477-1-oystwa@gmail.com>

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

Signed-off-by: Øystein Walle <oystwa@gmail.com>
---
 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.
 
 [[def_remote]]remote repository::
 	A <<def_repository,repository>> which is used to track the same
-- 
2.40.1
Next: Junio C Hamano
Message 1 of 2 in “Documentation: Mention that refspecs are explained elsewhere”
  1. Documentation: Mention that refspecs are explained elsewhereØystein Walle, May 6, 2024
  2. Junio C HamanoMay 6, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.