On 05/16/18 15:23, Jeff King wrote: > I implemented "repack -k", which keeps all objects and just rolls them > into the new pack (along with any currently-loose unreachable objects). > Aside from corner cases (e.g., where somebody accidentally added a 20GB > file to an otherwise 100MB-repo and then rolled it back), it usually > doesn't significantly affect the repository size. Hmm... I should read manpages more often! :) So, do you suggest that this is a better approach: - mother repos: "git repack -adk" - child repos: "git repack -Adl" (followed by prune) Currently, we do "-Adl" regardless, but we already track whether a repo is being used for alternates anywhere (so we don't prune it) and can do different flags if that improves performance. Best, -- Konstantin Ryabitsev Director, IT Infrastructure Security The Linux Foundation
Attachment:
signature.asc
Description: OpenPGP digital signature
