Hi, It seems a reasonable thing to do, as cloning the repo takes a lot of time now. We shouldn't have many pending pull requests as the release is coming, so I guess it's the right time to do that. After the appropriate communication on the mailing lists.
Thanks. Best regards, Jérôme 2015-12-22 11:20 GMT+01:00 Misagh Moayyed <[email protected]>: > I want to suggest that we attempt to reclaim some lost space in the > current git repo, which would tremendously help with future clones and the > release process in general. Currently, counting objects in the git repo’s > master branch tells me that the pack-size is somewhere around 803.27 MiB. > Running an aggressive prune strategy via git gc reduces that size down to > 280.55 which is a significant improvement. > > > > Here is how I ran tests on a temp fresh clone of master: > > > > git count-objects –vH > > git reflog expire --expire=now –all > > git gc --aggressive --prune=now > > git count-objects –vH > > > > Here is a very good walkthrough of how this may all be done: > > http://stevelorek.com/how-to-shrink-a-git-repository.html > > > > The caveat here is that all existing clones must either be rebased or > removed/cloned again. The repository history is rewritten, and all other > existing clones would become invalid. > > > > Does that sound reasonable? > > > > Misagh > > > > -- > You received this message because you are subscribed to the Google Groups > "CAS Developer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/. > -- You received this message because you are subscribed to the Google Groups "CAS Developer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.
