Jeff King a écrit :
I can't reproduce here, so presumably it is some condition in your
repository; can you make a tarball of your .git directory available?
Ok, mystery solved.
The problem was that the repository had been imported using git-svn and
contained something like 86000 reflog entries in
.git/logs/refs/remotes/pre/trunk.
Using the debugger I have seen that the loop was not endless... but very
slow as there was many many reflog to process. Don't know if this is
expected or not though.
To fix that I have launched:
$ git-reflog expire --expire=10 --all
It has removed all the old reflogs dating from the git-svn initial
import lowering the number of enties in .git/logs/refs/remotes/pre/trunk
to 0 :)
git gc is now working like a charm!
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
--
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
