Autogenerated HTML docs for v2.26.0-106-g9fade

1 files changed, 7 insertions, 5 deletions

diff --git a/git-pack-objects.html b/git-pack-objects.html
index 008afe995..bb34f4af7 100644
--- a/git-pack-objects.html
+++ b/git-pack-objects.html
@@ -754,7 +754,7 @@ git-pack-objects(1) Manual Page
         [--local] [--incremental] [--window=<n>] [--depth=<n>]

         [--revs [--unpacked | --all]] [--keep-pack=<pack-name>]

         [--stdout [--filter=<filter-spec>] | base-name]

-        [--shallow] [--keep-true-parents] [--sparse] &lt; object-list</pre>

+        [--shallow] [--keep-true-parents] [--[no-]sparse] &lt; object-list</pre>

 <div class="attribution">

 </div></div>

 </div>

@@ -1044,17 +1044,19 @@ depth is 4095.</p></div>
 </p>

 </dd>

 <dt class="hdlist1">

---sparse

+--[no-]sparse

 </dt>

 <dd>

 <p>

-        Use the "sparse" algorithm to determine which objects to include in

+        Toggle the "sparse" algorithm to determine which objects to include in

         the pack, when combined with the "--revs" option. This algorithm

         only walks trees that appear in paths that introduce new objects.

         This can have significant performance benefits when computing

         a pack to send a small change. However, it is possible that extra

         objects are added to the pack-file if the included commits contain

-        certain types of direct renames.

+        certain types of direct renames. If this option is not included,

+        it defaults to the value of <code>pack.useSparse</code>, which is true unless

+        otherwise specified.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1323,7 +1325,7 @@ over user-wide config, and so forth).</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2020-03-10 08:03:13 PDT

+ 2020-03-29 10:26:04 PDT

 </div>

 </div>

 </body>