aboutsummaryrefslogtreecommitdiff
path: root/Documentation/gitcore-tutorial.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-03-14 14:25:36 -0700
committerJunio C Hamano <gitster@pobox.com>2014-03-14 14:25:36 -0700
commitc923f603ea9288a8d44da994d9d0b4aea220dc99 (patch)
tree1948e4b2999723a7bfa87b1c26589d77c1ab74e6 /Documentation/gitcore-tutorial.txt
parent650c90a18506ce05e2be349d83fe1cef3dc7f8cb (diff)
parent2df85669d16703714968572937ebb67a31241ca3 (diff)
downloadgit-c923f603ea9288a8d44da994d9d0b4aea220dc99.tar.xz
Merge branch 'rt/links-for-asciidoctor'
* rt/links-for-asciidoctor: Documentation: fix documentation AsciiDoc links for external urls
Diffstat (limited to 'Documentation/gitcore-tutorial.txt')
-rw-r--r--Documentation/gitcore-tutorial.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt
index 058a352980..d2d7c213dd 100644
--- a/Documentation/gitcore-tutorial.txt
+++ b/Documentation/gitcore-tutorial.txt
@@ -1443,7 +1443,7 @@ Although Git is a truly distributed system, it is often
convenient to organize your project with an informal hierarchy
of developers. Linux kernel development is run this way. There
is a nice illustration (page 17, "Merges to Mainline") in
-link:http://www.xenotime.net/linux/mentor/linux-mentoring-2006.pdf[Randy Dunlap's presentation].
+http://www.xenotime.net/linux/mentor/linux-mentoring-2006.pdf[Randy Dunlap's presentation].
It should be stressed that this hierarchy is purely *informal*.
There is nothing fundamental in Git that enforces the "chain of