summaryrefslogtreecommitdiffstats
path: root/gittutorial.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2012-06-08 11:40:53 -0700
committerJunio C Hamano <gitster@pobox.com>2012-06-08 11:40:53 -0700
commit719b8a3137af7aea177e42a98cdfbb5180a10f33 (patch)
tree0b0aceeacfdab20db87a431a8a95e1388f0d9e19 /gittutorial.html
parent022bd341a82a08e16719ab8744973feed49e94d3 (diff)
downloadgit-htmldocs-719b8a3137af7aea177e42a98cdfbb5180a10f33.tar.gz
Autogenerated HTML docs for v1.7.11-rc2-2-g02101
Diffstat (limited to 'gittutorial.html')
-rw-r--r--gittutorial.html36
1 files changed, 18 insertions, 18 deletions
diff --git a/gittutorial.html b/gittutorial.html
index 848333166..534c3cd73 100644
--- a/gittutorial.html
+++ b/gittutorial.html
@@ -606,7 +606,7 @@ the first two chapters of <a href="user-manual.html">The Git User&#8217;s Manual
<pre><tt>$ git help log</tt></pre>
</div></div>
<div class="paragraph"><p>With the latter, you can use the manual viewer of your choice; see
-<a href="git-help.html">git-help(1)</a> for more information.</p></div>
+ for more information.</p></div>
<div class="paragraph"><p>It is a good idea to introduce yourself to git with your name and
public email address before doing any operation. The easiest
way to do so is:</p></div>
@@ -940,7 +940,7 @@ used for pulls:</p></div>
/home/alice/project</tt></pre>
</div></div>
<div class="paragraph"><p>(The complete configuration created by <em>git clone</em> is visible using
-<tt>git config -l</tt>, and the <a href="git-config.html">git-config(1)</a> man page
+<tt>git config -l</tt>, and the man page
explains the meaning of each option.)</p></div>
<div class="paragraph"><p>Git also keeps a pristine copy of Alice&#8217;s master branch under the
name "origin/master":</p></div>
@@ -956,10 +956,10 @@ perform clones and pulls using the ssh protocol:</p></div>
<pre><tt>bob$ git clone alice.org:/home/alice/project myrepo</tt></pre>
</div></div>
<div class="paragraph"><p>Alternatively, git has a native protocol, or can use rsync or http;
-see <a href="git-pull.html">git-pull(1)</a> for details.</p></div>
+see for details.</p></div>
<div class="paragraph"><p>Git can also be used in a CVS-like mode, with a central repository
-that various users push changes to; see <a href="git-push.html">git-push(1)</a> and
-<a href="gitcvs-migration.html">gitcvs-migration(7)</a>.</p></div>
+that various users push changes to; see and
+.</p></div>
</div>
<h2 id="_exploring_history">Exploring history</h2>
<div class="sectionbody">
@@ -1013,7 +1013,7 @@ $ git show HEAD^2 # show the second parent of HEAD</tt></pre>
<div class="paragraph"><p>you can refer to 1b2e1d63ff by the name "v2.5". If you intend to
share this name with other people (for example, to identify a release
version), you should create a "tag" object, and perhaps sign it; see
-<a href="git-tag.html">git-tag(1)</a> for details.</p></div>
+ for details.</p></div>
<div class="paragraph"><p>Any git command that needs to know a commit can take any of these
names. For example:</p></div>
<div class="listingblock">
@@ -1124,13 +1124,13 @@ The index file is a cache of the state of a directory tree,
</ul></div>
<div class="paragraph"><p>Part two of this tutorial explains the object
database, the index file, and a few other odds and ends that you&#8217;ll
-need to make the most of git. You can find it at <a href="gittutorial-2.html">gittutorial-2(7)</a>.</p></div>
+need to make the most of git. You can find it at .</p></div>
<div class="paragraph"><p>If you don&#8217;t want to continue with that right away, a few other
digressions that may be interesting at this point are:</p></div>
<div class="ulist"><ul>
<li>
<p>
-<a href="git-format-patch.html">git-format-patch(1)</a>, <a href="git-am.html">git-am(1)</a>: These convert
+, : These convert
series of git commits into emailed patches, and vice versa,
useful for projects such as the Linux kernel which rely heavily
on emailed patches.
@@ -1138,7 +1138,7 @@ digressions that may be interesting at this point are:</p></div>
</li>
<li>
<p>
-<a href="git-bisect.html">git-bisect(1)</a>: When there is a regression in your
+: When there is a regression in your
project, one way to track down the bug is by searching through
the history to find the exact commit that&#8217;s to blame. Git bisect
can help you perform a binary search for that commit. It is
@@ -1148,7 +1148,7 @@ digressions that may be interesting at this point are:</p></div>
</li>
<li>
<p>
-<a href="gitworkflows.html">gitworkflows(7)</a>: Gives an overview of recommended
+: Gives an overview of recommended
workflows.
</p>
</li>
@@ -1159,25 +1159,25 @@ digressions that may be interesting at this point are:</p></div>
</li>
<li>
<p>
-<a href="gitcvs-migration.html">gitcvs-migration(7)</a>: Git for CVS users.
+: Git for CVS users.
</p>
</li>
</ul></div>
</div>
<h2 id="_see_also">SEE ALSO</h2>
<div class="sectionbody">
-<div class="paragraph"><p><a href="gittutorial-2.html">gittutorial-2(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>,
-<a href="gitworkflows.html">gitworkflows(7)</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>