toni wrote:
> 1) "Hey what happens if i'm working with an up to date 3d chair model
> and comes the guy B and starts working with the same model?" Of course
> that's a BIG problem, is there any way to lock a file so nobody can
> update it from repository until it's commited again and then unlocked?
Not yet -- locking is a very-often-requested feature and will be added
to Subversion in future (I'm not sure of the schedule though). Depending
on your modelling tool it might be possible to obtain a merge tool that
can help you merge changes from multiple developers. Yes, this probably
isn't quite what you want for art assets, sorry! Things like AlienBrain
might be worth looking at (although they cost a fair bit).
> 2) "Hey, but models take lot of space, and i usually have lot of
> versions of a model, if it's all in repository, won't we run of out
> space quickly?" I told him "don't worry, probabhly you can purge all
> versions of something, excepting the last", am i right?
I think you're asking about "svn obliterate", which also doesn't exist
(yet). Subversion stores all files, including binaries, by efficiently
computing the difference between revisions, and just storing the diffs,
so it handles binaries way better than CVS. You could try storing some
models in a test repository, changing them, and watching how much space
you're using up.
Cheers,
Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 3 16:47:42 2004