aboutsummaryrefslogtreecommitdiff
path: root/Documentation/git-push.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-push.txt
parent69ae92bda13dfbf0b7d169c57b9f2715af2a9d67 (diff)
downloadgit-9d83e3827fc1031bbcafb0d26128e95dda306aed.tar.gz
git-9d83e3827fc1031bbcafb0d26128e95dda306aed.tar.xz
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-push.txt')
-rw-r--r--Documentation/git-push.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index 020955ff5..e11660a2e 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -41,7 +41,7 @@ OPTIONS[[OPTIONS]]
+
The <src> is often the name of the branch you would want to push, but
it can be any arbitrary "SHA-1 expression", such as `master~4` or
-`HEAD` (see linkgit:gitrevisions[1]).
+`HEAD` (see linkgit:gitrevisions[7]).
+
The <dst> tells which ref on the remote side is updated with this
push. Arbitrary expressions cannot be used here, an actual ref must