RE: Re: Recursive commit/update when checking out projects inside projects

----
It doesn't do what you want because it's not the right way to do it.
You can't put things into a working copy without telling the working
copy.
What you really want is svn:externals.
http://svnbook.red-b%e2%80%8bean.com/en/1.5/svn.a%e2%80%8bdvanced.externals.ht%e2%80%8bml
----
As I understand, externals are configured on the repository. As every user needs a different set of modules (and the list frequently changes for a user), they would all need their own subdirectory in the repository and manage  the externals? Auch :)
The externals page says:
"Sometimes it is useful to construct a working copy that is made out of a number of different checkouts. For example, you may want different subdirectories to come from different locations in a repository or perhaps from different repositories altogether. You could certainly set up such a scenario by hand—using svn checkout to create the sort of nested working copy structure you are trying to achieve. But if this layout is important for everyone who uses your repository, every other user will need to perform the same checkout operations that you did."
Well, what it describes there is exactly what I want: noone needs the same layout in their working copy, and I don't mind everyone using checkout to mix&match their own working copy of the main project tree, and the modules/plugins they're working on. 
But the problem I'm running into now, is that tortoisesvn isn't recursing across the 'checkout' boundaries in the working copy.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2419932
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].