Autogenerated HTML docs for v2.16.2-440-gc6284

1 files changed, 8 insertions, 8 deletions

diff --git a/gitsubmodules.html b/gitsubmodules.html
index 0443e5646..074bbb121 100644
--- a/gitsubmodules.html
+++ b/gitsubmodules.html
@@ -768,14 +768,14 @@ in is called a superproject.</p></div>
 consists of (i) a Git directory located under the <code>$GIT_DIR/modules/</code>

 directory of its superproject, (ii) a working directory inside the

 superproject&#8217;s working directory, and a <code>.git</code> file at the root of

-the submodule’s working directory pointing to (i).</p></div>

+the submodule&#8217;s working directory pointing to (i).</p></div>

 <div class="paragraph"><p>Assuming the submodule has a Git directory at <code>$GIT_DIR/modules/foo/</code>

 and a working directory at <code>path/to/bar/</code>, the superproject tracks the

 submodule via a <code>gitlink</code> entry in the tree at <code>path/to/bar</code> and an entry

 in its <code>.gitmodules</code> file (see <a href="gitmodules.html">gitmodules(5)</a>) of the form

 <code>submodule.foo.path = path/to/bar</code>.</p></div>

 <div class="paragraph"><p>The <code>gitlink</code> entry contains the object name of the commit that the

-superproject expects the submodule’s working directory to be at.</p></div>

+superproject expects the submodule&#8217;s working directory to be at.</p></div>

 <div class="paragraph"><p>The section <code>submodule.foo.*</code> in the <code>.gitmodules</code> file gives additional

 hints to Git&#8217;s porcelain layer. For example, the <code>submodule.foo.url</code>

 setting specifies where to obtain the submodule.</p></div>

@@ -912,20 +912,20 @@ the superproject. This is typically found in repositories generated
 using older versions of Git.

 </p>

 <div class="paragraph"><p>It is possible to construct these old form repositories manually.</p></div>

-<div class="paragraph"><p>When deinitialized or deleted (see below), the submodule’s Git

+<div class="paragraph"><p>When deinitialized or deleted (see below), the submodule&#8217;s Git

 directory is automatically moved to <code>$GIT_DIR/modules/&lt;name&gt;/</code>

 of the superproject.</p></div>

 </li>

 <li>

 <p>

 Deinitialized submodule: A <code>gitlink</code>, and a <code>.gitmodules</code> entry,

-but no submodule working directory. The submodule’s Git directory

+but no submodule working directory. The submodule&#8217;s Git directory

 may be there as after deinitializing the Git directory is kept around.

 The directory which is supposed to be the working directory is empty instead.

 </p>

 <div class="paragraph"><p>A submodule can be deinitialized by running <code>git submodule deinit</code>.

 Besides emptying the working directory, this command only modifies

-the superproject’s <code>$GIT_DIR/config</code> file, so the superproject’s history

+the superproject&#8217;s <code>$GIT_DIR/config</code> file, so the superproject&#8217;s history

 is not affected. This can be undone using <code>git submodule init</code>.</p></div>

 </li>

 <li>

@@ -934,9 +934,9 @@ Deleted submodule: A submodule can be deleted by running
 <code>git rm &lt;submodule path&gt; &amp;&amp; git commit</code>. This can be undone

 using <code>git revert</code>.

 </p>

-<div class="paragraph"><p>The deletion removes the superproject’s tracking data, which are

+<div class="paragraph"><p>The deletion removes the superproject&#8217;s tracking data, which are

 both the <code>gitlink</code> entry and the section in the <code>.gitmodules</code> file.

-The submodule’s working directory is removed from the file

+The submodule&#8217;s working directory is removed from the file

 system, but the Git directory is kept around as it to make it

 possible to checkout past commits without requiring fetching

 from another repository.</p></div>

@@ -1092,7 +1092,7 @@ your working tree. Alternatively you can set <em>submodule.recurse</em> to have
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2018-02-13 17:28:38 PST

+ 2018-03-06 15:25:02 PST

 </div>

 </div>

 </body>