@matheusbsbs / matheus-bagliano / commits / b85c4bbbd7
Fork 0

Documentation: Fix broken links

core-tutorial.txt, cvs-migration.txt, tutorial-2.txt: Fix broken links. Signed-off-by: Dmitry V. Levin <ldv@altlinux.org> Signed-off-by: Junio C Hamano <junkio@cox.net>

Dmitry V. Levin committed Sep 14, 2006 at 05:04 UTC b85c4bbbd7d16c084f0b2f0eb9678149d08d09e8
3 files changed +3 -3
Documentation/core-tutorial.txt
+1 -1
@@ -1620,7 +1620,7 @@ suggested in the previous section may be new to you. You do not
1620 have to worry. git supports "shared public repository" style of
1621 cooperation you are probably more familiar with as well.
1622
1623 -See link:cvs-migration.txt[git for CVS users] for the details.
1623 +See link:cvs-migration.html[git for CVS users] for the details.
1624
1625 Bundling your work together
1626 ---------------------------
Documentation/cvs-migration.txt
+1 -1
@@ -172,7 +172,7 @@ Advanced Shared Repository Management
172
173 Git allows you to specify scripts called "hooks" to be run at certain
174 points. You can use these, for example, to send all commits to the shared
175 -repository to a mailing list. See link:hooks.txt[Hooks used by git].
175 +repository to a mailing list. See link:hooks.html[Hooks used by git].
176
177 You can enforce finer grained permissions using update hooks. See
178 link:howto/update-hook-example.txt[Controlling access to branches using
Documentation/tutorial-2.txt
+1 -1
@@ -368,7 +368,7 @@ in the index file is identical to the one in the working directory.
368 In addition to being the staging area for new commits, the index file
369 is also populated from the object database when checking out a
370 branch, and is used to hold the trees involved in a merge operation.
371 -See the link:core-tutorial.txt[core tutorial] and the relevant man
371 +See the link:core-tutorial.html[core tutorial] and the relevant man
372 pages for details.
373
374 What next?