summaryrefslogtreecommitdiffstats
path: root/git-pack-objects.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2019-02-06 23:20:47 -0800
committerJunio C Hamano <gitster@pobox.com>2019-02-06 23:20:47 -0800
commit23168ef89678fc52e01173bbc7fdaa760f21d02a (patch)
tree8425bac71f938dfce77a3c2928b2c936b03789c9 /git-pack-objects.txt
parent2567b326fac6961a6fc6075ad2f22a744252f2f3 (diff)
downloadgit-htmldocs-23168ef89678fc52e01173bbc7fdaa760f21d02a.tar.gz
Autogenerated HTML docs for v2.21.0-rc0
Diffstat (limited to 'git-pack-objects.txt')
-rw-r--r--git-pack-objects.txt11
1 files changed, 10 insertions, 1 deletions
diff --git a/git-pack-objects.txt b/git-pack-objects.txt
index 40c825c38..e45f3e680 100644
--- a/git-pack-objects.txt
+++ b/git-pack-objects.txt
@@ -14,7 +14,7 @@ SYNOPSIS
[--local] [--incremental] [--window=<n>] [--depth=<n>]
[--revs [--unpacked | --all]] [--keep-pack=<pack-name>]
[--stdout [--filter=<filter-spec>] | base-name]
- [--shallow] [--keep-true-parents] < object-list
+ [--shallow] [--keep-true-parents] [--sparse] < object-list
DESCRIPTION
@@ -196,6 +196,15 @@ depth is 4095.
Add --no-reuse-object if you want to force a uniform compression
level on all data no matter the source.
+--sparse::
+ Use 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.
+
--thin::
Create a "thin" pack by omitting the common objects between a
sender and a receiver in order to reduce network transfer. This