diff options
author | 2017-04-26 15:39:11 +0900 | |
---|---|---|
committer | 2017-04-26 15:39:11 +0900 | |
commit | 7ba7bff6294153449453b27ebdcb2ad2e751736d (patch) | |
tree | 0e822e864d529bb0aa563c22d9b174f31526adc3 /Documentation/gitcore-tutorial.txt | |
parent | Merge branch 'sf/putty-w-args' (diff) | |
parent | docs/bisect-lk2009: update java code conventions link (diff) | |
download | tgif-7ba7bff6294153449453b27ebdcb2ad2e751736d.tar.xz |
Merge branch 'jk/update-links-in-docs'
Many stale HTTP(s) links have been updated in our documentation.
* jk/update-links-in-docs:
docs/bisect-lk2009: update java code conventions link
docs/bisect-lk2009: update nist report link
docs/archimport: quote sourcecontrol.net reference
gitcore-tutorial: update broken link
doc: replace or.cz gitwiki link with git.wiki.kernel.org
doc: use https links to avoid http redirect
Diffstat (limited to 'Documentation/gitcore-tutorial.txt')
-rw-r--r-- | Documentation/gitcore-tutorial.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt index 3a0ec8c53a..7577f27ec2 100644 --- a/Documentation/gitcore-tutorial.txt +++ b/Documentation/gitcore-tutorial.txt @@ -1429,7 +1429,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 -http://www.xenotime.net/linux/mentor/linux-mentoring-2006.pdf[Randy Dunlap's presentation]. +https://web.archive.org/web/20120915203609/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 |