summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: bf3478d)
raw | patch | inline | side by side (parent: bf3478d)
author | Junio C Hamano <junkio@cox.net> | |
Sat, 3 Feb 2007 07:17:34 +0000 (23:17 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Sat, 3 Feb 2007 07:17:34 +0000 (23:17 -0800) |
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/core-tutorial.txt | patch | blob | history |
index 1cd834b0ff8347db4f32717a30b47a23cb51adfa..9c28bea62e5848e30137c063ca8fa91de737ca01 100644 (file)
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