Vega Strike Forums

How big is the repo?

or

Anyone know how bit the entire vs history is if cloned as a git repository?

I once pulled all of trunk when we where using cvs which did not have tags or that many branches at the time i forget exactly how many Gb it took up and this was before we had added the masters folder to the repo for art assets ie..blend and full size textures,sounds so it would now be much larger but this was in XP and that drive went ticky,tocky about three years ago so i lost it I was a bit of a noob with versioning systems then might be able to find our current space usage on the sourceforge servers as i don't have commit rights i don't know for sure.

Enjoy the Choice

The data and vegastrike folder in the trunk are around 1.5 GB
And i think trunk and all the tags/branches are between 5 and 12 GB in total me be even more.

When did the project switch from CVS to Subversion?

some ware in 2006/2007

It was at that point that sourceforge first offered subversion service actually and they did promote it a bit heavily.

Enjoy the Choice

I'm glad they did! The only thing I know how to do in CVS is checkout a module... and at that I have to look it up.

FINALLY after about 30 hours I've checked out the subversion repository into git!

Bare Size: 2.7G
With master checked out: 4.3G

I was afraid it would be more.

That would fit on a double layer DVD with room to spare

Enjoy the Choice

Actually you can simply load the git repository without the working copy. that is 2.7GB currently. It contains the ENTIRE project history... well... I haven't dug into it at all yet. During the checkout process I kind of had to monitor it because the process would stop for some reason. I did the "clone" on my desktop and monitored it on my laptop over my vpn. Next is to move the repo to my laptop since I now know how much space I need. I was afraid it would be like 50GB or so.
Git makes branching and merging easy, I'll have access to all branches, can do some cool things like re-basing. I can incrementally update my repo from svn and if I had commit access commit changes back to svn. Also I can generate a patch that can be submitted to someone that has commit access. The other nice thing is I can now privately branch, merge and commit my own code, then publish what is good and destroy what is not.
Also there may be something to it's submodule support. I'll be looking into PU's compatibility with the dev versions of the engine. I can checkout the PU data as a submodule in git. This effectively binds a particular commit of PU to a particular commit of VS that can be updated, branched and so forth independent from VS, along with being cloned separately. KDE has or is moving their project from subversion to git and are using submodules so people can clone PARTS of the project as git doesn't handle that like svn does.