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

1 files changed, 8 insertions, 8 deletions

diff --git a/git-submodule.html b/git-submodule.html
index 44cb5f30d..7828f8b2a 100644
--- a/git-submodule.html
+++ b/git-submodule.html
@@ -616,7 +616,7 @@ if you choose to go that route.</p></div>
 <div class="paragraph"><p>Submodules are composed from a so-called <tt>gitlink</tt> tree entry

 in the main repository that refers to a particular commit object

 within the inner repository that is completely separate.

-A record in the <tt>.gitmodules</tt> (see <a href="gitmodules.html">gitmodules(5)</a>) file at the

+A record in the <tt>.gitmodules</tt> (see ) file at the

 root of the source tree assigns a logical name to the submodule and

 describes the default URL the submodule shall be cloned from.

 The logical name can be used for overriding this URL within your

@@ -695,7 +695,7 @@ status
 submodules, and show their status as well.</p></div>

 <div class="paragraph"><p>If you are only interested in changes of the currently initialized

 submodules with respect to the commit recorded in the index or the HEAD,

-<a href="git-status.html">git-status(1)</a> and <a href="git-diff.html">git-diff(1)</a> will provide that information

+ and  will provide that information

 too (and can also report changes to a submodule&#8217;s work tree).</p></div>

 </dd>

 <dt class="hdlist1">

@@ -748,7 +748,7 @@ summary
         (this option doesn&#8217;t allow to use the <tt>--cached</tt> option or to provide an

         explicit commit).

 </p>

-<div class="paragraph"><p>Using the <tt>--submodule=log</tt> option with <a href="git-diff.html">git-diff(1)</a> will provide that

+<div class="paragraph"><p>Using the <tt>--submodule=log</tt> option with  will provide that

 information too.</p></div>

 </dd>

 <dt class="hdlist1">

@@ -903,7 +903,7 @@ sync
         Rebase the current branch onto the commit recorded in the

         superproject. If this option is given, the submodule&#8217;s HEAD will not

         be detached. If a merge failure prevents this process, you will have

-        to resolve these failures with <a href="git-rebase.html">git-rebase(1)</a>.

+        to resolve these failures with .

         If the key <tt>submodule.$name.update</tt> is set to <tt>rebase</tt>, this option is

         implicit.

 </p>

@@ -925,10 +925,10 @@ sync
 <p>

         This option is only valid for add and update commands.  These

         commands sometimes need to clone a remote repository. In this case,

-        this option will be passed to the <a href="git-clone.html">git-clone(1)</a> command.

+        this option will be passed to the  command.

 </p>

 <div class="paragraph"><p><strong>NOTE</strong>: Do <strong>not</strong> use this option unless you have read the note

-for <a href="git-clone.html">git-clone(1)</a>'s <tt>--reference</tt> and <tt>--shared</tt> options carefully.</p></div>

+for 's <tt>--reference</tt> and <tt>--shared</tt> options carefully.</p></div>

 </dd>

 <dt class="hdlist1">

 --recursive

@@ -958,12 +958,12 @@ for <a href="git-clone.html">git-clone(1)</a>'s <tt>--reference</tt> and <tt>--s
 <div class="paragraph"><p>When initializing submodules, a .gitmodules file in the top-level directory

 of the containing repository is used to find the url of each submodule.

 This file should be formatted in the same way as <tt>$GIT_DIR/config</tt>. The key

-to each submodule url is "submodule.$name.url".  See <a href="gitmodules.html">gitmodules(5)</a>

+to each submodule url is "submodule.$name.url".  See 

 for details.</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>