aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/git-check-ref-format.txt
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2010-10-11 11:03:32 -0500
committerJunio C Hamano <gitster@pobox.com>2010-10-13 19:10:55 -0700
commit9d83e3827fc1031bbcafb0d26128e95dda306aed (patch)
treed6a0338f158a915a40b9ee8f216ca974426ea158 /Documentation/git-check-ref-format.txt
parent69ae92bda13dfbf0b7d169c57b9f2715af2a9d67 (diff)
downloadgit-9d83e3827fc1031bbcafb0d26128e95dda306aed.tar.gz
Documentation: gitrevisions is in section 7
Fix references to gitrevisions(1) in the manual pages and HTML documentation. In practice, this will not matter much unless someone tries to use a hard copy of the git reference manual. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-check-ref-format.txt')
-rw-r--r--Documentation/git-check-ref-format.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt
index f5c2e0601d..205d83dd0b 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:gitrevisions[1]):
+reference name expressions (see linkgit:gitrevisions[7]):
. A double-dot `..` is often used as in `ref1..ref2`, and in some
contexts this notation means `{caret}ref1 ref2` (i.e. not in