Autogenerated HTML docs for v1.7.11-rc2-2-g02101

1 files changed, 12 insertions, 12 deletions

diff --git a/gittutorial-2.html b/gittutorial-2.html
index ae3b6fdb6..2cb57b12b 100644
--- a/gittutorial-2.html
+++ b/gittutorial-2.html
@@ -589,7 +589,7 @@ gittutorial-2(7) Manual Page
 </div>

 <h2 id="_description">DESCRIPTION</h2>

 <div class="sectionbody">

-<div class="paragraph"><p>You should work through <a href="gittutorial.html">gittutorial(7)</a> before reading this tutorial.</p></div>

+<div class="paragraph"><p>You should work through  before reading this tutorial.</p></div>

 <div class="paragraph"><p>The goal of this tutorial is to introduce two fundamental pieces of

 git&#8217;s architecture&#8212;the object database and the index file&#8212;and to

 provide the reader with everything necessary to understand the rest

@@ -745,7 +745,7 @@ to have multiple parents.   In that case the commit represents a
 merge, with the parent references pointing to the heads of the merged

 branches.</p></div>

 <div class="paragraph"><p>Besides blobs, trees, and commits, the only remaining type of object

-is a "tag", which we won&#8217;t discuss here; refer to <a href="git-tag.html">git-tag(1)</a>

+is a "tag", which we won&#8217;t discuss here; refer to 

 for details.</p></div>

 <div class="paragraph"><p>So now we know how git uses the object database to represent a

 project&#8217;s history:</p></div>

@@ -953,7 +953,7 @@ in the index file is identical to the one in the working directory.</p></div>
 <div class="paragraph"><p>In addition to being the staging area for new commits, the index file

 is also populated from the object database when checking out a

 branch, and is used to hold the trees involved in a merge operation.

-See <a href="gitcore-tutorial.html">gitcore-tutorial(7)</a> and the relevant man

+See  and the relevant man

 pages for details.</p></div>

 </div>

 <h2 id="_what_next">What next?</h2>

@@ -961,31 +961,31 @@ pages for details.</p></div>
 <div class="paragraph"><p>At this point you should know everything necessary to read the man

 pages for any of the git commands; one good place to start would be

 with the commands mentioned in <a href="everyday.html">Everyday git</a>.  You

-should be able to find any unknown jargon in <a href="gitglossary.html">gitglossary(7)</a>.</p></div>

+should be able to find any unknown jargon in .</p></div>

 <div class="paragraph"><p>The <a href="user-manual.html">Git User&#8217;s Manual</a> provides a more

 comprehensive introduction to git.</p></div>

-<div class="paragraph"><p><a href="gitcvs-migration.html">gitcvs-migration(7)</a> explains how to

+<div class="paragraph"><p> explains how to

 import a CVS repository into git, and shows how to use git in a

 CVS-like way.</p></div>

 <div class="paragraph"><p>For some interesting examples of git use, see the

 <a href="howto-index.html">howtos</a>.</p></div>

-<div class="paragraph"><p>For git developers, <a href="gitcore-tutorial.html">gitcore-tutorial(7)</a> goes

+<div class="paragraph"><p>For git developers,  goes

 into detail on the lower-level git mechanisms involved in, for

 example, creating a new commit.</p></div>

 </div>

 <h2 id="_see_also">SEE ALSO</h2>

 <div class="sectionbody">

-<div class="paragraph"><p><a href="gittutorial.html">gittutorial(7)</a>,

-<a href="gitcvs-migration.html">gitcvs-migration(7)</a>,

-<a href="gitcore-tutorial.html">gitcore-tutorial(7)</a>,

-<a href="gitglossary.html">gitglossary(7)</a>,

-<a href="git-help.html">git-help(1)</a>,

+<div class="paragraph"><p>,

+,

+,

+,

+,

 <a href="everyday.html">Everyday git</a>,

 <a href="user-manual.html">The Git User&#8217;s Manual</a></p></div>

 </div>

 <h2 id="_git">GIT</h2>

 <div class="sectionbody">

-<div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite.</p></div>

+<div class="paragraph"><p>Part of the  suite.</p></div>

 </div>

 </div>

 <div id="footnotes"><hr /></div>