Josh Pieper wrote:
>Branko ??ibej wrote:
>
>
>>Josh Pieper wrote:
>>
>>
>>
>>>I don't understand. Are you saying that some portions of file:// URLs
>>>are not given directly to the filesystem to resolve? Or that we can
>>>safely collapse "/../" paths from them? Or something else?
>>>
>>>
>>>
>>>
>>Both, but the second is more important. I think we should consider
>>removing the '/../' portions from file:// URLs. Whilst we can't do that
>>safely in paths -- because of the order in which symlinks get resolved,
>>as I now understand -- I think we can safely forbid this kind of symlink
>>magic for canonical repository URLs and simply declare that these don't
>>contain /../ and /./ sequences. That would let us handle all URLs the same.
>>
>>
>
>Brane,
>
>ghudson, breser and myself talked a little on IRC and think that just
>generating a sane error if any URLs contain "/../", and not collapsing
>".." in paths would be an acceptable solution for now. What do you
>think?
>
>
I'm happy with that. The result is that we don't get any "non-canonical"
URLs into the libraries, which is basically what I was aiming for. Thanks.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 6 23:37:32 2004