From: Jeff King <peff@peff.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH] Documentation: convert uses of git-link macro to gitlink
Date: Wed, 2 Aug 2006 12:32:32 -0400 [thread overview]
Message-ID: <20060802163231.GA22107@coredump.intra.peff.net> (raw)
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
reply other threads:[~2006-08-02 16:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060802163231.GA22107@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox