Skip to content

Commit f991c62

Browse files
peffgitster
authored andcommitted
gitcore-tutorial: update broken link
The slides for the Linux-mentoring presentation are no longer available. Let's point to the wayback version of the page, which works. Note that the referenced diagram is also available on page 15 of [1]. We could link to that instead, but it's not clear from the URL scheme ("uploads") whether it's going to stick around forever. [1] https://www.linuxfoundation.jp/jp_uploads/seminar20070313/Randy.pdf Signed-off-by: Jeff King <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 02ba23f commit f991c62

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Documentation/gitcore-tutorial.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1429,7 +1429,7 @@ Although Git is a truly distributed system, it is often
14291429
convenient to organize your project with an informal hierarchy
14301430
of developers. Linux kernel development is run this way. There
14311431
is a nice illustration (page 17, "Merges to Mainline") in
1432-
http://www.xenotime.net/linux/mentor/linux-mentoring-2006.pdf[Randy Dunlap's presentation].
1432+
https://web.archive.org/web/20120915203609/http://www.xenotime.net/linux/mentor/linux-mentoring-2006.pdf[Randy Dunlap's presentation].
14331433

14341434
It should be stressed that this hierarchy is purely *informal*.
14351435
There is nothing fundamental in Git that enforces the "chain of

0 commit comments

Comments
 (0)