I did some work with dulwich, a pure python implementation of Git. What I am about to say here reflects my experience with dulwich’s git implementation, not the canonical git source and so there may be differences. Git is remarkably simple – I mean, so simple it confounds! The name is really appropriate to its … Read more
I had the same problem, tried the solutions mentioned so far without success. But my problems with git gc began after I added big image files to repo, so I created .gitattributes file and turned off delta compression for those big files: *.tga -delta *.psd -delta It worked.
git is supposed to be always safe from interruptions like this. If you are worried, though, I suggest Ctrl+Z and then run a git fsck –full to make sure the system is consistent. There are a number of git-config variables which might help your git-gc go faster. I use the following on one particular large … Read more
As Jefromi commented on Dan’s answer, git gc should be called automatically called during “normal” use of a bare repository. I just ran git gc –aggressive on two bare, shared repositories that have been actively used; one with about 38 commits the past 3-4 weeks, and the other with about 488 commits over roughly 3 … Read more
I used instructions from this link. Same idea as Charles Baileys suggested. A copy of the commands is here: git config –global pack.windowMemory “100m” git config –global pack.packSizeLimit “100m” git config –global pack.threads “1” This worked for me on hostgator with shared hosting account.
The remote repo should be configured to run gc as needed after a commit is made. See the documentation of gc.auto in git-gc and git-config man pages. However, a remote repo shouldn’t need all that much garbage collection, since it will rarely have dangling (unreachable) commits. These usually result from things like branch deletion and … Read more
Since nobody had yet an answer, I looked into the code to see how to remove the code which shows up that dialog. I found the hint_gc procedure which does it and the place where it is called. At the same time I noticed that late 2011 there was added a configuration option for disabling … Read more
It depends mostly on how much the repository is used. With one user checking in once a day and a branch/merge/etc operation once a week you probably don’t need to run it more than once a year. With several dozen developers working on several dozen projects each checking in 2-3 times a day, you might … Read more
Maybe it’s too late to post a reply, but as this page is the first Google’s result, it may still be helpful. If you want to free some space in your git repo, but do not want to rebuild all your commits (rebase or graft), and still be able to push/pull/merge from people who has … Read more
I don’t understand the ramifications of this, but as suggested in this thread, when I encountered this I just did $ mv .git/refs/remotes/origin/HEAD /tmp (keeping it around just in case) and then $ git gc worked without complaining; I haven’t run into any problems.