git gc --aggressive
Indeed, size went from 93 MB to 12 MB this time :)
I guess size will expand after some commits and the command can be
run again, but it's better to have a small repo when you want to do a
quick local "clone" of the repo by just doing "cp -r repo repo_new"
That size is really a little bit weird. I guess it must have grown that
big on my HD since I used to sync my git tree with "hg-fast-export"
with the mercurial tree since last summer. Sorry for that.
I'm a little bit afraid that the repo on the server is now also 120 MB
big already. I wonder whether we can somehow trigger the garbage
collection on the server side, too? Or should we maybe rather destroy
the repo again and start with a fresh and small one?