diff options
| author | Junio C Hamano <gitster@pobox.com> | 2017-04-26 19:21:51 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2017-04-26 19:21:51 -0700 |
| commit | beca34013bc0864f462092d897371034e5e76810 (patch) | |
| tree | 4caf7e3a0c5c71fda031f7dad119560744a714ae /gitcore-tutorial.html | |
| parent | e25cc817fa321686ae71fda302e172bf9ca8f04a (diff) | |
| download | git-htmldocs-beca34013bc0864f462092d897371034e5e76810.tar.gz | |
Autogenerated HTML docs for v2.13.0-rc1
Diffstat (limited to 'gitcore-tutorial.html')
| -rw-r--r-- | gitcore-tutorial.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gitcore-tutorial.html b/gitcore-tutorial.html index 4e0faecdb..84fd3e756 100644 --- a/gitcore-tutorial.html +++ b/gitcore-tutorial.html @@ -2169,7 +2169,7 @@ repositories every once in a while.</p></div> 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
-<a href="http://www.xenotime.net/linux/mentor/linux-mentoring-2006.pdf">Randy Dunlap’s presentation</a>.</p></div>
+<a href="https://web.archive.org/web/20120915203609/http://www.xenotime.net/linux/mentor/linux-mentoring-2006.pdf">Randy Dunlap’s presentation</a>.</p></div>
<div class="paragraph"><p>It should be stressed that this hierarchy is purely <strong>informal</strong>.
There is nothing fundamental in Git that enforces the "chain of
patch flow" this hierarchy implies. You do not have to pull
@@ -2457,7 +2457,7 @@ to follow, not easier.</p></div> <div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2017-02-15 15:17:51 PST
+Last updated 2017-04-26 19:19:22 PDT
</div>
</div>
</body>
|