> I think that Thorsten perhaps misunderstood your problem. I just
> tested this with Subersion 1.7.8 on a local file based repository, and
> when you're trying to *set* svn:externals, you do need a local working
> copy of the directory you're setting svn:externals for. TortoiseSVN
> does provide wonderful views into the existing upstream repository and
> its configurations, but I'm sure does not allow *directly* setting
> these properties in the repo itself, because it's not in the basic
> "svn" command itself.
>
>
Thanks for your reply.
If svn:external require working copy, then it can be implemented
only in client side basis right?
If i want my entire team to use a uniform svn folder structure, then
should i need to configure the folder structure via svn:external one by one?
Can't i just configure the svn repository structure in the server side and
let my team check out the entire svn repository with all related folders
linked using svn external ?
Received on 2013-01-13 10:17:40 CET