summaryrefslogtreecommitdiffstats
path: root/user-manual.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2007-05-13 22:19:53 +0000
committerJunio C Hamano <junio@hera.kernel.org>2007-05-13 22:19:53 +0000
commit323e52dd2e49bceead5c67a881e8dc79db63e52c (patch)
tree5b1a478ec7701ceacff59b27a0e2029cf7ca476e /user-manual.txt
parent8638c92248aa3a950fe0a206e702f5c35d69fa35 (diff)
downloadgit-htmldocs-323e52dd2e49bceead5c67a881e8dc79db63e52c.tar.gz
Autogenerated HTML docs for v1.5.2-rc3-27-g43d151
Diffstat (limited to 'user-manual.txt')
-rw-r--r--user-manual.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/user-manual.txt b/user-manual.txt
index 13db9699c..a7abeaa1d 100644
--- a/user-manual.txt
+++ b/user-manual.txt
@@ -1875,7 +1875,7 @@ $ chmod a+x hooks/post-update
(For an explanation of the last two lines, see
gitlink:git-update-server-info[1], and the documentation
-link:hooks.txt[Hooks used by git].)
+link:hooks.html[Hooks used by git].)
Advertise the url of proj.git. Anybody else should then be able to
clone or pull from that url, for example with a commandline like:
@@ -1959,7 +1959,7 @@ Setting up a shared repository
Another way to collaborate is by using a model similar to that
commonly used in CVS, where several developers with special rights
all push to and pull from a single shared repository. See
-link:cvs-migration.txt[git for CVS users] for instructions on how to
+link:cvs-migration.html[git for CVS users] for instructions on how to
set this up.
[[setting-up-gitweb]]