>>
>> a_trunk/
>> svn/
>> ...
>> wc/
>> src/
>> something/
>>
>> This sounds good initially but fairly clearly introduces a fairly
>> significant condition. the .svn handling for folder 'something'
>> needs
>> to know that, rather than ./.svn/ it must look for svndata in
>> ../../../svn/... (or whatever the locative ends up being).
>
> Right. And that would seem to be a performance hit for using a
> working copy. Instead of Subversion looking in one known place
> (the .svn directory in the current directory), it has to look in
> potentially all parent directories to discover whether the thing
> even is a working copy.
>
>
I've used systems like this (perforce) .. Walking "up" the tree was
never a performance issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 00:58:58 2006