From: Franck Date: Thu, 17 Nov 2005 10:36:47 GMT Subject: Re: [QUESTION] Access to a huge GIT repository. Message-ID: In-Reply-To: Hi Linus 2005/11/16, Linus Torvalds : > > > First off, "rsync://" will never do what you want. It uses rsync > (surprised surprise) to grab the objects, so since it has no clue what the > objects are, it has no choice but to just grab them all. > yes that was a bad example, actually I've tried several protocol including git protocol. > The fact that _some_ of the linux-mips repositories are based on mine > makes me suspect that all their 2.6-based ones are rooted like mine is, > but that may or may not be true. > hmm, don't think "linux mips" repository is rooted like yours. It seems that it has been imported from mips cvs repository which contains linux-mips history since 1995. > Just try your above command line with "git://" instead. > > (NOTE! Doing a full clone like the above is pretty expensive with git for > the server side, so it might take a while before it starts feeding you > stuff if it is under heavy load) > well I've already tried that but have renounced after waiting more than 4 hours ! I don't know if the server was under heavy load or if git protocol needs a lots of resources but it seems useless to setup a git dameon on it... > If you want to get rid of other branches, do: Sorry, I forget to tell that I have already tried what you suggested at first (except that I did not do a 'git repack -a -d') but it didn't work out (and that the reason why I tried the "kill father object" thing). Since I forgot the repack thing, I retried again, and it did last more than 4 hours to cpmplete all git commands. After that I run gitk --all to check that all old branch's objects have been removed but I can see all of them. I plan to take look at git code to understand how object removal is done, but until this do you have any ideas why this fails ? Thanks -- Franck