Wed, 26 Jan 2011 13:37:59 +0900, Jae-Joon Lee wrote:
[clip]
I spend an hour to figure out how we can delete these unreachable
objects. But it turned out that the answer seems to be simple.$ git repack -ad
The complete magic stanza is:
git reflog expire --expire=0 --all
git prune
git repack -f -a -d
git gc --prune=0
Wonderful!
With this, I get about 40 MB!
Regards,
-JJ
On Wed, Jan 26, 2011 at 7:28 PM, Pauli Virtanen <pav@...278...> wrote:
The complete magic stanza is:
git reflog expire --expire=0 --all
git prune
git repack -f -a -d
git gc --prune=0
How did you manage to do that? Using these steps (which have been
added to the postprocess.sh script):
On Wed, Jan 26, 2011 at 6:35 AM, Jae-Joon Lee <lee.j.joon@...149...> wrote:
On Wed, Jan 26, 2011 at 7:28 PM, Pauli Virtanen <pav@...278...> wrote:
The complete magic stanza is:
git reflog expire --expire=0 --all
git prune
git repack -f -a -d
git gc --prune=0Wonderful!
With this, I get about 40 MB!
---
run git filter-branch --index-filter \
'git rm --cached --ignore-unmatch release/osx/matplotlib-0.98.5.tar.gz' \
-- 750059aa09340^..
rm -Rf refs/original
rm -Rf logs
run git reflog expire --expire=0 --all
run git prune
run git repack -f -a -d --depth=250 --window=250
run git gc --prune=0
---
I only get down to 65 MB, at which point "git fsck --unreachable HEAD"
indicates a slew of unreachable blobs, trees, and commits, one of
which is:
3b8b6c010f8ce59afac1e811b1bbc3efc21b770a release/osx/matplotlib-0.98.5.tar.gz
yet "git log --pretty=oneline -- release/osx/matplotlib-0.98.5.tar.gz"
shows it is no longer associated with any commits. Rerunning the
"reflog/prune/repack/gc" block doesn't seem to help at this point.