Re: [PATCH v5 00/11] Create 'expire' and 'repack' verbs for git-multi-pack-index
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 25, 2019, 05:38 UTC
- Message-ID
- <xmqqbm0uy78e.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <20190424151428.170316-1-dstolee@microsoft.com>
Derrick Stolee <stolee@gmail.com> writes:
Show 14 quoted lines
> Updates in V5: > > * Fixed the error in PATCH 7 due to a missing line that existed in PATCH 8. Thanks, Josh Steadmon! > > * The 'repack' subcommand now computes the "expected size" of a pack instead of > relying on the total size of the pack. This is actually really important to > the way VFS for Git uses prefetch packs, and some packs are not being > repacked because the pack size is larger than the batch size, but really > there are only a few referenced objects. > > * The 'repack' subcommand now allows a batch size of zero to mean "create one > pack containing all objects in the multi-pack-index". A new commit adds a > test that hits the boundary cases here, but follows the 'expire' subcommand > so we can show that cycle of repack-then-expire to safely replace the packs.
I guess all of them need to tweak the authorship from the gmail address to the work address on the Signed-off-by: trailer, which I can do (as I noticed it before applying).