@@ -99,12 +99,23 @@ pack.packSizeLimit::
9999 packing to a file when repacking, i.e. the git:// protocol
100100 is unaffected. It can be overridden by the `--max-pack-size`
101101 option of linkgit:git-repack[1]. Reaching this limit results
102- in the creation of multiple packfiles; which in turn prevents
103- bitmaps from being created.
104- The minimum size allowed is limited to 1 MiB.
105- The default is unlimited.
106- Common unit suffixes of 'k', 'm', or 'g' are
107- supported.
102+ in the creation of multiple packfiles.
103+ +
104+ Note that this option is rarely useful, and may result in a larger total
105+ on-disk size (because Git will not store deltas between packs), as well
106+ as worse runtime performance (object lookup within multiple packs is
107+ slower than a single pack, and optimizations like reachability bitmaps
108+ cannot cope with multiple packs).
109+ +
110+ If you need to actively run Git using smaller packfiles (e.g., because your
111+ filesystem does not support large files), this option may help. But if
112+ your goal is to transmit a packfile over a medium that supports limited
113+ sizes (e.g., removable media that cannot store the whole repository),
114+ you are likely better off creating a single large packfile and splitting
115+ it using a generic multi-volume archive tool (e.g., Unix `split`).
116+ +
117+ The minimum size allowed is limited to 1 MiB. The default is unlimited.
118+ Common unit suffixes of 'k', 'm', or 'g' are supported.
108119
109120pack.useBitmaps::
110121 When true, git will use pack bitmaps (if available) when packing
0 commit comments