Junio C Hamano [off-list ref] writes:
But a "gc" does not necessarily run "repack -a" when it does not see
too many pack files, so it can end up scanning only the surface of
the history to collect the recently created loose objects into a
pack, and stop its traversal without going into existing packfiles.
Isn't that the behavior of "git gc --auto", not plain "git gc" ?
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/