One idea: How about using just one repository, but shaped like this:

trunk/
branches/
tags/

then a next level (example from inside trunk):

trunk/code/
trunk/data/
trunk/originals/

so if you wanted to download the latest of all, you would do svn up on
trunk, while if you wanted to just grab a new code branch, you'd do
svn up on trunk/code only.

I do not see what you gain from using separate repositories, instead
of separate directories inside a single repository. Am I missing
something? I think it is a feature that with a single repository we
would still have one global revision ID for everything, so you could
say, "test revision NNN", instead of "test code revision NNN with data
revision MMM".

  - Per

_______________________________________________
Warzone-dev mailing list
[email protected]
https://mail.gna.org/listinfo/warzone-dev

Reply via email to