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

[PATCH] Documentation: convert uses of git-link macro to gitlink

From
Jeff King <peff@peff.net>
Date
Aug 2, 2006, 16:32 UTC
Message-ID
<20060802163231.GA22107@coredump.intra.peff.net>
There isn't and never was such a macro; all uses are typos.
Signed-off-by: Jeff King <peff@peff.net>
---
 Documentation/config.txt        |    6 +++---
 Documentation/git-cvsimport.txt |    2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index e669003..d89916b 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -223,14 +223,14 @@ showbranch.default::
 	See gitlink:git-show-branch[1].
 
 tar.umask::
-	By default, git-link:git-tar-tree[1] sets file and directories modes
+	By default, gitlink:git-tar-tree[1] sets file and directories modes
 	to 0666 or 0777. While this is both useful and acceptable for projects
 	such as the Linux Kernel, it might be excessive for other projects.
 	With this variable, it becomes possible to tell
-	git-link:git-tar-tree[1] to apply a specific umask to the modes above.
+	gitlink:git-tar-tree[1] to apply a specific umask to the modes above.
 	The special value "user" indicates that the user's current umask will
 	be used. This should be enough for most projects, as it will lead to
-	the same permissions as git-link:git-checkout[1] would use. The default
+	the same permissions as gitlink:git-checkout[1] would use. The default
 	value remains 0, which means world read-write.
 
 user.email::
diff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt
index b0c6d7c..d21d66b 100644
--- a/Documentation/git-cvsimport.txt
+++ b/Documentation/git-cvsimport.txt
@@ -116,7 +116,7 @@ file each time git-cvsimport is run.
 +
 It is not recommended to use this feature if you intend to
 export changes back to CVS again later with
-git-link[1]::git-cvsexportcommit.
+gitlink:git-cvsexportcommit[1].
 
 OUTPUT
 ------
-- 
1.4.2.rc2.g59706-dirty
Message 1 of 1 in “Documentation: convert uses of git-link macro to gitlink”
  1. Documentation: convert uses of git-link macro to gitlinkJeff King, Aug 2, 2006

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.