path: root/Documentation/git-check-ref-format.txt
diff options
authorJunio C Hamano <>2010-07-15 19:07:01 (GMT)
committerJunio C Hamano <>2010-07-15 19:07:01 (GMT)
commitcb597adb5cb989540ebd77afc9507cd24d6c70bd (patch)
tree419c2a4d58ee81efb1f6518814160ca4fb0ffa40 /Documentation/git-check-ref-format.txt
parentbff6e86b3d01febaa2d73ff4e890f091999e9e28 (diff)
parentf028cdae6663166ebfd777e73aacce1f5e7159d6 (diff)
Merge branch 'mg/revision-doc'
* mg/revision-doc: Documentation: link to gitrevisions rather than git-rev-parse Documentation: gitrevisions Documentation: split off rev doc into include file
Diffstat (limited to 'Documentation/git-check-ref-format.txt')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt
index 379eee6..f5c2e06 100644
--- a/Documentation/git-check-ref-format.txt
+++ b/Documentation/git-check-ref-format.txt
@@ -49,7 +49,7 @@ git imposes the following rules on how references are named:
These rules make it easy for shell script based tools to parse
reference names, pathname expansion by the shell when a reference name is used
unquoted (by mistake), and also avoids ambiguities in certain
-reference name expressions (see linkgit:git-rev-parse[1]):
+reference name expressions (see linkgit:gitrevisions[1]):
. A double-dot `..` is often used as in `ref1..ref2`, and in some
contexts this notation means `{caret}ref1 ref2` (i.e. not in