summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <junkio@cox.net>2007-02-02 23:17:34 -0800
committerLibravatar Junio C Hamano <junkio@cox.net>2007-02-02 23:17:34 -0800
commit505739f6c0c67b7426ffbc723734c794b0a810d9 (patch)
tree298677c18064adf1bbc20646a95cd927558a5414 /Documentation
parentTutorial-2: Adjust git-status output to recent reality. (diff)
downloadtgif-505739f6c0c67b7426ffbc723734c794b0a810d9.tar.xz
core-tutorial: http reference link fix
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/core-tutorial.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/core-tutorial.txt b/Documentation/core-tutorial.txt
index 1cd834b0ff..9c28bea62e 100644
--- a/Documentation/core-tutorial.txt
+++ b/Documentation/core-tutorial.txt
@@ -1469,8 +1469,8 @@ Working with Others
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 Randy
-Dunlap's presentation (`http://tinyurl.com/a2jdg`).
+is a nice illustration (page 17, "Merges to Mainline") in
+link:http://tinyurl.com/a2jdg[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