On 9 December 2014 at 14:14, Jeff King <p...@peff.net> wrote: > On Mon, Dec 08, 2014 at 05:22:23PM +0100, Martin Scherer wrote: > >> # invoke bfg --delete-folders something multiple times with different >> pattern. >> >> # try to cleanup >> >> git gc --aggressive --prune=now # big blobs still in history >> git fsck # no results >> git fsck --full --unreachable --dangling # no results > > Might you still have reflogs pointing to the objects? Try: > > git reflog expire --expire-unreachable=now --all
Yeah, we figured that's what it was! https://github.com/rtyley/bfg-repo-cleaner/issues/62#issuecomment-66152559 > I also don't know if BFG keeps backup refs around (filter-branch, for > example, writes a copy of the original refs into refs/original; you > would want to delete that if you're trying to slim down the repo). The BFG reports the ref changes to the command line (and outputs a full list of changed object-ids in repo-name.git.bfg-report/[datetime]/object-id-map.old-new.txt) but doesn't keep refs (like refs/original) around because that would get in the way of the BFG's explicit intended use-case of removing unwanted data. Thanks for the object-size checking scripts, very useful. Roberto -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
