git documentation says that to reduce the size of the repository can use git clone --local, git clone --reference, but we did not get the repository smaller than the repository derived from _shared_clone. We can't get repo size before clone in normal way, only if add some post-receive hook http://stackoverflow.com/questions/28678223/estimate-the-size-of-a-git-repository-before-cloning-it
--- ** [tickets:#8042] Better handing of tmp dirs during merge** **Status:** in-progress **Milestone:** unreleased **Labels:** stability sf-current 42cc sf-2 **Created:** Thu Jan 07, 2016 10:54 PM UTC by Dave Brondsema **Last Updated:** Wed Jan 13, 2016 03:06 PM UTC **Owner:** Igor Bondarenko Doing a one-click merge of a very large repo can potentially cause problems if the working dir is bigger than the tmp dir mount supports. * `def merge` can use a try/finally so that `shutil.rmtree` always runs even if the clone fails (e.g. out of disk space) * see if its possible to a shared clone (see also `_shared_clone`) so the object files don't have to get copied, reducing disk usage and execution time. It'd be nice if we could set a max size limit and check that in `can_merge` or `merge_allowed` but it doesn't seem to be a way to check the size of a working copy ahead of time. There is `git count-objects -vH` but that's just the repo size, not the working copy. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
