Actually, after using git-gc, git-repack isn't really needed... git-gc identifies that the two files are very similar and re-deltifies (see the du -s -k outputs in the original mail, after git-gc we have in fact lower usage than the first commit). My question is basically... (a) why doesn't git detect this during commit and needs a git-gc (b) whether after git-gc I would have seen the massive difference during a subsequent git-push or not Thanassis. > Have you tried to git repack with aggressive options, like: > > git repack --window=500 --depth=500 \ > --window-memory=<fair amount of your physical RAM> -- What I gave, I have; what I spent, I had; what I kept, I lost. -Old Epitaph -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
