On Jan 25, 2010, at 07:25, trans wrote: > Is it possible to keep tags/ and branches/ in the trunk/ so as not to > have to differentiate these three at the top of a repository. > > In other words, instead of: > > branches/ > BRANCH_xyz/ > tags/ > RELEASE_1_0_0/ > trunk/ > README > bin/ > lib/ > > One could have: > > README > bin/ > branches/ > BRANCH_xyz/ > lib/ > tags/ > RELEASE_1_0_0/ > > I think I might prefer this approach, if possible. The problem of > course is in creating new tags and branches, i.e. making a copy, I > would need to prevent the tags/ and branches/ directories from being > copied in the process. Is there a way to do that?
I'm going to go with a firm "no" on this one. Do not attempt to do this. Instead, follow the standard layout. In your scheme, not only, as you've noticed, would checking out the trunk also check out all branches and all tags, which would be wasteful, it also prevents you from using the usual way to create tags, i.e. copying the trunk to the branches or tags directory -- in your scheme, you can't do this, because you can't copy a directory into itself. $ svn cp trunk trunk/branches/foo svn: Cannot copy path 'trunk' into its own child 'trunk/branches/foo'
