> Second, you wouldn't want to get the trunk and all the branches
> and all the tags whenever you check out or update libs (or even
> just lib1, as in your example) would you? So I guess your plan
> is to check out, for example, libs/lib1/trunk calling it "lib1"
> as your working directory name as you do so, eh?
>
> Perhaps this is a philosophical choice, but I don't see why you
> would want to have dozens or even hundreds of directories named
> trunk, branches, and tags when you could have just one of each.
(just one of each in the local filesystem, or just one of each in the
repository...?)
Yes, I think I'm asking the same question. If you follow the examples
in the subversion book, the "recommended" way to set up the repository is
with trunk/branches/tags directories under each project (in my case, lib1
lib2 lib3...project1 project2..etc)
So I guess I'm asking what the pros and cons are to having the
trunk/tags/branches dirs on a per-project basis vs. a per repository
basis..
-Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 29 04:14:37 2004