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

1 files changed, 8 insertions, 9 deletions

diff --git a/git-update-index.html b/git-update-index.html
index de779df09..2512bf2ad 100644
--- a/git-update-index.html
+++ b/git-update-index.html
@@ -604,7 +604,7 @@ git-update-index(1) Manual Page
 <div class="paragraph"><p>Modifies the index or directory cache. Each file mentioned is updated

 into the index and any <em>unmerged</em> or <em>needs updating</em> state is

 cleared.</p></div>

-<div class="paragraph"><p>See also <a href="git-add.html">git-add(1)</a> for a more user-friendly way to do some of

+<div class="paragraph"><p>See also  for a more user-friendly way to do some of

 the most common operations on the index.</p></div>

 <div class="paragraph"><p>The way <em>git update-index</em> handles files it is told about can be modified

 using the various options:</p></div>

@@ -967,7 +967,7 @@ tree files, you have to explicitly tell git about it by dropping
 <div class="paragraph"><p>In order to set "assume unchanged" bit, use <tt>--assume-unchanged</tt>

 option.  To unset, use <tt>--no-assume-unchanged</tt>. To see which files

 have the "assume unchanged" bit set, use <tt>git ls-files -v</tt>

-(see <a href="git-ls-files.html">git-ls-files(1)</a>).</p></div>

+(see ).</p></div>

 <div class="paragraph"><p>The command looks at <tt>core.ignorestat</tt> configuration variable.  When

 this is true, paths updated with <tt>git update-index paths...</tt> and

 paths updated with other git commands that update both index and

@@ -1077,13 +1077,13 @@ precedence over assume-unchanged bit when both are set.</p></div>
 <div class="sectionbody">

 <div class="paragraph"><p>The command honors <tt>core.filemode</tt> configuration variable.  If

 your repository is on a filesystem whose executable bits are

-unreliable, this should be set to <em>false</em> (see <a href="git-config.html">git-config(1)</a>).

+unreliable, this should be set to <em>false</em> (see ).

 This causes the command to ignore differences in file modes recorded

 in the index and the file mode on the filesystem if they differ only on

 executable bit.   On such an unfortunate filesystem, you may

 need to use <em>git update-index --chmod=</em>.</p></div>

 <div class="paragraph"><p>Quite similarly, if <tt>core.symlinks</tt> configuration variable is set

-to <em>false</em> (see <a href="git-config.html">git-config(1)</a>), symbolic links are checked out

+to <em>false</em> (see ), symbolic links are checked out

 as plain files, and this command does not modify a recorded file mode

 from symbolic link to regular file.</p></div>

 <div class="paragraph"><p>The command looks at <tt>core.ignorestat</tt> configuration variable.  See

@@ -1091,17 +1091,16 @@ from symbolic link to regular file.</p></div>
 <div class="paragraph"><p>The command also looks at <tt>core.trustctime</tt> configuration variable.

 It can be useful when the inode change time is regularly modified by

 something outside Git (file system crawlers and backup systems use

-ctime for marking files processed) (see <a href="git-config.html">git-config(1)</a>).</p></div>

+ctime for marking files processed) (see ).</p></div>

 </div>

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

 <div class="sectionbody">

-<div class="paragraph"><p><a href="git-config.html">git-config(1)</a>,

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

-<a href="git-ls-files.html">git-ls-files(1)</a></p></div>

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

+,</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>