On Sat, 10 Jun 2006, Martin Langhoff wrote: > > Exactly. The dog at this time is cvsps -- I also remember vague > promises from a list regular of publishing a git repo with cvsps2.1 + > some patches from the list. Ahh. cvsps doesn't do anything incrementally, does it? Although it _does_ build up a cache of sorts, I think. That's not the parts I actually ever ended up looking at. But yeah, a cvsps that blows up to a gig of VM and takes half an hour to parse things just for an incremental update would be a problem. > In any case, and for the record, my cvsps is 2.1 pristine. It handles > the mozilla repo alright, as long as I give it a lot of RAM. I _think_ > it slurped 3GB with the mozilla cvs. Oh, wow. Every single repo I've seen ends up having tons of complaints from pristine cvsps, but maybe that's because I only end up looking at the ones with problems ;) > I'm coming down to the office now to pick up my laptop, and I'll rsync > it out to our git machine (also NZ kernel mirror, bandwidth should be > good). That's one of the things I've discovered with these large > trees: for the initial publish action, I just use rsync or scp. > Perhaps I'm doing it wrong, but git-push doesn't optimise the > 'initialise repo', and it take ages (and it this case, it'd probably > OOM). > > > So it will take me quite some time to download 2GB+, regardless of how fat > > a pipe the other end has ;) > > Right-o. Linus, Jon, can you guys then ping me when you have cloned it > safely so I can take it down again? Tell me where/when it is, and I'll start slurping. Will let you know when I'm done. Linus - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html