summaryrefslogtreecommitdiff
path: root/log-tree.c
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2016-06-13 00:38:04 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-06-14 13:57:45 -0700
commite26a8c4721ceaf4c59e33bbd4e60f777b7ea9b62 (patch)
tree621b15b1697fda207311a48baf647cce59c53c9e /log-tree.c
parentrepack: add --keep-unreachable option (diff)
downloadtgif-e26a8c4721ceaf4c59e33bbd4e60f777b7ea9b62.tar.xz
repack: extend --keep-unreachable to loose objects
If you use "repack -adk" currently, we will pack all objects that are already packed into the new pack, and then drop the old packs. However, loose unreachable objects will be left as-is. In theory these are meant to expire eventually with "git prune". But if you are using "repack -k", you probably want to keep things forever and therefore do not run "git prune" at all. Meaning those loose objects may build up over time and end up fooling any object-count heuristics (such as the one done by "gc --auto", though since git-gc does not support "repack -k", this really applies to whatever custom scripts people might have driving "repack -k"). With this patch, we instead stuff any loose unreachable objects into the pack along with the already-packed unreachable objects. This may seem wasteful, but it is really no more so than using "repack -k" in the first place. We are at a slight disadvantage, in that we have no useful ordering for the result, or names to hand to the delta code. However, this is again no worse than what "repack -k" is already doing for the packed objects. The packing of these objects doesn't matter much because they should not be accessed frequently (unless they actually _do_ become referenced, but then they would get moved to a different part of the packfile during the next repack). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'log-tree.c')
0 files changed, 0 insertions, 0 deletions