A shallow clone certainly shouldn't be as large as a normal one. Something's
borked.
On Sun, 10 Mar 2013 22:39:44 +0100, Chad <innocentkiller(a)gmail.com> wrote:
- We can repack core on manganese. This should
provide a bit of relief,
but won't help long term. Core would have to be read-only for about an hour
or two.
This should be just done already, and repeated from time to time. The repo is growing in
size much quicker than it should (full clone now is over 250 MB, in September it was under
180 MB IIRC).
-We can rewrite history (git-filter-branch) to remove
some mistakes that
exploded the repo size. Binaries later removed, things accidentally checked
into ./extensions, etc. This could potentially greatly reduce object sizes
and allow for tighter repacks. Major issue with history rewriting is
everyone will have to reclone (all sha1s would change). I've not tested my
theory yet.
Ugh, the nuclear option. Let's try repacking first, can we? :) This is probably going
to make gerrit a little unhappy when it's database thing gets inconsistent with the
repo.
--
Matma Rex