Karl Fogel wrote:
>Philip Martin <philip@codematters.co.uk> writes:
>
>>>I think there should be no need to canonicalize them -- they should
>>>already be in canonical form. If they're not, that's a bug we'd want
>>>revealed anyway (?)...
>>>
>>Hmmm....
>>
>>$ svn co -d ~/wc http://svn.collab.net:81/repos/svn/trunk/tools/dev
>>$ svn co -d ~/wc http://svn.collab.net:81/repos/svn/trunk//tools/dev
>>
>>../svn/subversion/libsvn_wc/adm_files.c:1125
>>svn_error: #21034 : <Obstructed update>
>> URL 'http://svn.collab.net:81/repos/svn/trunk//tools/dev' doesn't match existing URL 'http://svn.collab.net:81/repos/svn/trunk/tools/dev' in '/home/pm/wc'
>>
>
>Urg. Hmmm. Nice experiment :-).
>
>So, should we canonicalize URLs before using them, or just not depend
>on them being canonicalized? I lean toward the former, so that
>comparisons are reliable. But I have a feeling someone (or somemany)
>have thought deeply on this question already, and will have something
>unexpected to say...
>
The same rules apply as for local paths: the client is responsible for
utf-8'ing and canonicalizing URLs and paths before passing them off into
the SVN APIs. Right now, of course, the client doesn't do that. :-)
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 6 21:43:33 2002