Autogenerated HTML docs for v2.6.2-367-g80980a

gitster · Oct 29, 2015 · ee61580 · ee61580
1 parent daf0aae
commit ee61580
Show file tree

Hide file tree

Showing 23 changed files with 51 additions and 28 deletions.
diff --git a/RelNotes/1.7.7.txt b/RelNotes/1.7.7.txt
@@ -84,7 +84,7 @@ Updates since v1.7.6
    logic used by "git diff" to determine the hunk header.
 
  * Invoking the low-level "git http-fetch" without "-a" option (which
-   git itself never did---normal users should not have to worry about
+   git itself never did--normal users should not have to worry about
    this) is now deprecated.
 
  * The "--decorate" option to "git log" and its family learned to

diff --git a/RelNotes/1.8.3.1.txt b/RelNotes/1.8.3.1.txt
@@ -1,5 +1,5 @@
 Git v1.8.3.1 Release Notes
-========================
+==========================
 
 Fixes since v1.8.3
 ------------------

diff --git a/RelNotes/1.8.4.1.txt b/RelNotes/1.8.4.1.txt
@@ -1,5 +1,5 @@
 Git v1.8.4.1 Release Notes
-========================
+==========================
 
 Fixes since v1.8.4
 ------------------

diff --git a/RelNotes/1.8.4.2.txt b/RelNotes/1.8.4.2.txt
@@ -1,5 +1,5 @@
 Git v1.8.4.2 Release Notes
-========================
+==========================
 
 Fixes since v1.8.4.1
 --------------------

diff --git a/RelNotes/1.8.4.3.txt b/RelNotes/1.8.4.3.txt
@@ -1,5 +1,5 @@
 Git v1.8.4.3 Release Notes
-========================
+==========================
 
 Fixes since v1.8.4.2
 --------------------

diff --git a/RelNotes/1.8.4.4.txt b/RelNotes/1.8.4.4.txt
@@ -1,5 +1,5 @@
 Git v1.8.4.4 Release Notes
-========================
+==========================
 
 Fixes since v1.8.4.3
 --------------------

diff --git a/RelNotes/1.9.0.txt b/RelNotes/1.9.0.txt
@@ -177,7 +177,7 @@ Performance, Internal Implementation, etc.
  * The naming convention of the packfiles has been updated; it used to
    be based on the enumeration of names of the objects that are
    contained in the pack, but now it also depends on how the packed
-   result is represented---packing the same set of objects using
+   result is represented--packing the same set of objects using
    different settings (or delta order) would produce a pack with
    different name.
 

diff --git a/RelNotes/2.7.0.txt b/RelNotes/2.7.0.txt
@@ -97,6 +97,13 @@ Performance, Internal Implementation, Development Support etc.
    of "git stripspace" has been updated to use the parse_options API.
    (merge bed4452 tk/stripspace later to maint).
 
+ * "git am" used to spawn "git mailinfo" via run_command() API once
+   per each patch, but learned to make a direct call to mailinfo()
+   instead.
+
+ * The implementation of "git mailinfo" was refactored so that a
+   mailinfo() function can be directly called from inside a process.
+
 
 Also contains various documentation updates and code clean-ups.
 
@@ -258,7 +265,20 @@ notes for details).
    never die, which is not the case (yet).
    (merge c63d4b2 jc/am-3-fallback-regression-fix later to maint).
 
- * Code clean-up and minor fixes.
+ * The linkage order of libraries was wrong in places around libcurl.
+   (merge 7e91e8d rp/link-curl-before-ssl later to maint).
+
+ * The name-hash subsystem that is used to cope with case insensitive
+   filesystems keeps track of directories and their on-filesystem
+   cases for all the paths in the index by holding a pointer to a
+   randomly chosen cache entry that is inside the directory (for its
+   ce->ce_name component).  This pointer was not updated even when the
+   cache entry was removed from the index, leading to use after free.
+   This was fixed by recording the path for each directory instead of
+   borrowing cache entries and restructuring the API somewhat.
+   (merge 41284eb dt/name-hash-dir-entry-fix later to maint).
+
+ * Code clean-up, minor fixes etc.
    (merge 15ed07d jc/rerere later to maint).
    (merge e7a7401 pt/pull-builtin later to maint).
    (merge 29bc480 nd/ls-remote-does-not-have-u-option later to maint).
@@ -269,3 +289,6 @@ notes for details).
    (merge 44cd91e cc/quote-comments later to maint).
    (merge 147875f sb/submodule-config-parse later to maint).
    (merge ae9f274 es/worktree-add later to maint).
+   (merge 3b19dba jc/em-dash-in-doc later to maint).
+   (merge f3f38c7 jc/everyday-markup later to maint).
+   (merge 77d5f71 xf/user-manual-markup later to maint).
diff --git a/git-bisect.html b/git-bisect.html
@@ -1031,7 +1031,7 @@ <h3 id="_bisect_run">Bisect run</h3>
 revision will be skipped (see <code>git bisect skip</code> above). 125 was chosen
 as the highest sensible value to use for this purpose, because 126 and 127
 are used by POSIX shells to signal specific error status (127 is for
-command not found, 126 is for command found but not executable---these
+command not found, 126 is for command found but not executable&#8212;these
 details do not matter, as they are normal errors in the script, as far as
 <code>bisect run</code> is concerned).</p></div>
 <div class="paragraph"><p>You may often find that during a bisect session you want to have
@@ -1227,7 +1227,7 @@ <h2 id="_git">GIT</h2>
 <div id="footnotes"><hr /></div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2015-10-05 13:38:43 PDT
+Last updated 2015-10-29 14:44:28 PDT
 </div>
 </div>
 </body>

diff --git a/git-bisect.txt b/git-bisect.txt
@@ -256,7 +256,7 @@ Then compile and test the chosen revision, and afterwards mark
 the revision as good or bad in the usual manner.
 
 Bisect skip
-~~~~~~~~~~~~
+~~~~~~~~~~~
 
 Instead of choosing a nearby commit by yourself, you can ask Git to do
 it for you by issuing the command:
@@ -335,7 +335,7 @@ cannot be tested. If the script exits with this code, the current
 revision will be skipped (see `git bisect skip` above). 125 was chosen
 as the highest sensible value to use for this purpose, because 126 and 127
 are used by POSIX shells to signal specific error status (127 is for
-command not found, 126 is for command found but not executable---these
+command not found, 126 is for command found but not executable--these
 details do not matter, as they are normal errors in the script, as far as
 `bisect run` is concerned).
 

diff --git a/git-fetch.html b/git-fetch.html
@@ -1369,7 +1369,7 @@ <h2 id="_configured_remote_tracking_branches_a_id_crtb_a">CONFIGURED REMOTE-TRAC
 When <code>git fetch</code> is run without specifying what branches
   and/or tags to fetch on the command line, e.g. <code>git fetch origin</code>
   or <code>git fetch</code>, <code>remote.&lt;repository&gt;.fetch</code> values are used as
-  the refspecs---they specify which refs to fetch and which local refs
+  the refspecs&#8212;they specify which refs to fetch and which local refs
   to update.  The example above will fetch
   all branches that exist in the <code>origin</code> (i.e. any ref that matches
   the left-hand side of the value, <code>refs/heads/*</code>) and update the
@@ -1480,7 +1480,7 @@ <h2 id="_git">GIT</h2>
 <div id="footnotes"><hr /></div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2015-03-23 14:31:16 PDT
+Last updated 2015-10-29 14:44:28 PDT
 </div>
 </div>
 </body>

diff --git a/git-fetch.txt b/git-fetch.txt
@@ -71,7 +71,7 @@ This configuration is used in two ways:
 * When `git fetch` is run without specifying what branches
   and/or tags to fetch on the command line, e.g. `git fetch origin`
   or `git fetch`, `remote.<repository>.fetch` values are used as
-  the refspecs---they specify which refs to fetch and which local refs
+  the refspecs--they specify which refs to fetch and which local refs
   to update.  The example above will fetch
   all branches that exist in the `origin` (i.e. any ref that matches
   the left-hand side of the value, `refs/heads/*`) and update the

diff --git a/git-push.html b/git-push.html
@@ -811,7 +811,7 @@ <h2 id="_options_a_id_options_a">OPTIONS<a id="OPTIONS"></a></h2>
 If <code>git push [&lt;repository&gt;]</code> without any <code>&lt;refspec&gt;</code> argument is set to
 update some ref at the destination with <code>&lt;src&gt;</code> with
 <code>remote.&lt;repository&gt;.push</code> configuration variable, <code>:&lt;dst&gt;</code> part can
-be omitted---such a push will update a ref that <code>&lt;src&gt;</code> normally updates
+be omitted&#8212;such a push will update a ref that <code>&lt;src&gt;</code> normally updates
 without any <code>&lt;refspec&gt;</code> on the command line.  Otherwise, missing
 <code>:&lt;dst&gt;</code> means to update the same ref as the <code>&lt;src&gt;</code>.</p></div>
 <div class="paragraph"><p>The object referenced by &lt;src&gt; is used to update the &lt;dst&gt; reference
@@ -1748,7 +1748,7 @@ <h2 id="_git">GIT</h2>
 <div id="footnotes"><hr /></div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2015-08-31 16:04:31 PDT
+Last updated 2015-10-29 14:44:28 PDT
 </div>
 </div>
 </body>

diff --git a/git-push.txt b/git-push.txt
@@ -62,7 +62,7 @@ be named.
 If `git push [<repository>]` without any `<refspec>` argument is set to
 update some ref at the destination with `<src>` with
 `remote.<repository>.push` configuration variable, `:<dst>` part can
-be omitted---such a push will update a ref that `<src>` normally updates
+be omitted--such a push will update a ref that `<src>` normally updates
 without any `<refspec>` on the command line.  Otherwise, missing
 `:<dst>` means to update the same ref as the `<src>`.
 +

diff --git a/git-remote.txt b/git-remote.txt
@@ -1,5 +1,5 @@
 git-remote(1)
-============
+=============
 
 NAME
 ----

diff --git a/git-upload-archive.txt b/git-upload-archive.txt
@@ -1,5 +1,5 @@
 git-upload-archive(1)
-====================
+=====================
 
 NAME
 ----

diff --git a/giteveryday.txt b/giteveryday.txt
@@ -1,5 +1,5 @@
 giteveryday(7)
-===============
+==============
 
 NAME
 ----

diff --git a/gitrevisions.txt b/gitrevisions.txt
@@ -1,5 +1,5 @@
 gitrevisions(7)
-================
+===============
 
 NAME
 ----

diff --git a/technical/index-format.html b/technical/index-format.html
@@ -1036,7 +1036,7 @@ <h3 id="_cached_tree">Cached tree</h3>
 <div class="content">
 <pre><code>The entries are written out in the top-down, depth-first order.  The
 first entry represents the root level of the repository, followed by the
-first subtree---let's call this A---of the root level (with its name
+first subtree--let's call this A--of the root level (with its name
 relative to the root level), followed by the first subtree of A (with
 its name relative to A), ...</code></pre>
 </div></div>
@@ -1278,7 +1278,7 @@ <h2 id="_untracked_cache">Untracked cache</h2>
 <div id="footnotes"><hr /></div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2015-08-19 15:39:41 PDT
+Last updated 2015-10-29 14:44:28 PDT
 </div>
 </div>
 </body>

diff --git a/technical/index-format.txt b/technical/index-format.txt
@@ -170,7 +170,7 @@ Git index format
 
   The entries are written out in the top-down, depth-first order.  The
   first entry represents the root level of the repository, followed by the
-  first subtree---let's call this A---of the root level (with its name
+  first subtree--let's call this A--of the root level (with its name
   relative to the root level), followed by the first subtree of A (with
   its name relative to A), ...
 

diff --git a/urls-remotes.txt b/urls-remotes.txt
@@ -36,7 +36,7 @@ The `<pushurl>` is used for pushes only. It is optional and defaults
 to `<url>`.
 
 Named file in `$GIT_DIR/remotes`
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 You can choose to provide the name of a
 file in `$GIT_DIR/remotes`.  The URL

diff --git a/user-manual.html b/user-manual.html
diff --git a/user-manual.txt b/user-manual.txt
@@ -1491,7 +1491,7 @@ resolving a merge>>.
 
 [[fixing-a-mistake-by-rewriting-history]]
 Fixing a mistake by rewriting history
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If the problematic commit is the most recent commit, and you have not
 yet made that commit public, then you may just