From: Sitaram Chamarty Date: Sun, 18 Nov 2012 10:42:06 GMT Subject: Re: Local clones aka forks disk size optimization Message-ID: In-Reply-To: On Fri, Nov 16, 2012 at 11:34 PM, Enrico Weigelt wrote: > >> Provide one "main" clone which is bare, pulls automatically, and is >> there to stay (no pruning), so that all others can use that as a >> reliable alternates source. > > The problem here, IMHO, is the assumption, that the main repo will > never be cleaned up. But what to do if you dont wanna let it grow > forever ? That's not the only problem. I believe you only get the savings when the main repo gets the commits first. Which is probably ok most of the time but it's worth mentioning. > > hmm, distributed GC is a tricky problem. Except for one little issue (see other thread, subject line "cloning a namespace downloads all the objects"), namespaces appear to do everything we want in terms of the typical use cases for alternates, and/or 'git clone -l', at least on the server side.