From: Franck Date: Tue, 22 Nov 2005 19:10:26 GMT Subject: Re: [QUESTION] Access to a huge GIT repository. Message-ID: In-Reply-To: <7v1x18fw8j.fsf@assigned-by-dhcp.cox.net> 2005/11/22, Junio C Hamano : > Were you around on this list, around the beginning of this > month? nope, I subscribed to the list one week later. > The thread that starts here may be of interest: > > http://marc.theaimsgroup.com/?l=git&m=113089701819420 > > I think (although I do not exactly know how the "lite" > repository was constructed) what you are doing is similar to > what I called "shallow clone" there in that thread. Indeed. What I'm doing to get my "shallow clone" is basicaly remove every ref/branchs I don't want, then run git-prune, git-repack -a -d. But the result should be the same as your "shallow clone" method. > At the end > of the thread I think I listed what you can and cannot do in > such an incomplete repository. > Yes. But the big difference is that, in my case, the shallow copy is used as a public repository, whereas in your case the shallow copy is used as a working repository. Anyway, Ralf (the mips arch maintainer) is going to create a new pruned repository that should resolve my problem. I'm going to wait for it instead of trying to make my own "broken" repository. Thanks -- Franck