{"thread":{"id":"5556","subject":"[PATCH] Documentation: Fix broken links","startedAt":"2006-09-14T01:04:33Z","lastAt":"2006-09-14T01:04:33Z","messageCount":1,"participants":["Dmitry V. Levin"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"26854","messageId":"20060914010433.GC20593@nomad.office.altlinux.org","threadId":"5556","inReplyTo":null,"subject":"[PATCH] Documentation: Fix broken links","fromName":"Dmitry V. Levin","fromEmail":"ldv@altlinux.org","sentAt":"2006-09-14T01:04:33Z","receivedAt":"2006-09-14T01:04:33Z","isPatch":true,"sender":{"key":"ldv@altlinux.org","avatar":"https://avatars.githubusercontent.com/u/5281408?v=4"},"body":"core-tutorial.txt, cvs-migration.txt, tutorial-2.txt:\n\tFix broken links.\n\nSigned-off-by: Dmitry V. Levin <ldv@altlinux.org>\n---\n Documentation/core-tutorial.txt |    2 +-\n Documentation/cvs-migration.txt |    2 +-\n Documentation/tutorial-2.txt    |    2 +-\n 3 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/core-tutorial.txt b/Documentation/core-tutorial.txt\nindex 1185897..47505aa 100644\n--- a/Documentation/core-tutorial.txt\n+++ b/Documentation/core-tutorial.txt\n@@ -1620,7 +1620,7 @@ suggested in the previous section may be\n have to worry. git supports \"shared public repository\" style of\n cooperation you are probably more familiar with as well.\n \n-See link:cvs-migration.txt[git for CVS users] for the details.\n+See link:cvs-migration.html[git for CVS users] for the details.\n \n Bundling your work together\n ---------------------------\ndiff --git a/Documentation/cvs-migration.txt b/Documentation/cvs-migration.txt\nindex d2b0bd3..6812683 100644\n--- a/Documentation/cvs-migration.txt\n+++ b/Documentation/cvs-migration.txt\n@@ -172,7 +172,7 @@ Advanced Shared Repository Management\n \n Git allows you to specify scripts called \"hooks\" to be run at certain\n points.  You can use these, for example, to send all commits to the shared\n-repository to a mailing list.  See link:hooks.txt[Hooks used by git].\n+repository to a mailing list.  See link:hooks.html[Hooks used by git].\n \n You can enforce finer grained permissions using update hooks.  See\n link:howto/update-hook-example.txt[Controlling access to branches using\ndiff --git a/Documentation/tutorial-2.txt b/Documentation/tutorial-2.txt\nindex 2f4fe12..42b6e7d 100644\n--- a/Documentation/tutorial-2.txt\n+++ b/Documentation/tutorial-2.txt\n@@ -368,7 +368,7 @@ in the index file is identical to the on\n In addition to being the staging area for new commits, the index file\n is also populated from the object database when checking out a\n branch, and is used to hold the trees involved in a merge operation.\n-See the link:core-tutorial.txt[core tutorial] and the relevant man\n+See the link:core-tutorial.html[core tutorial] and the relevant man\n pages for details.\n \n What next?\n\n\n-- \nldv\n"}]}