Re: BUG (?) in svn cp

++ 02/03/04 19:46 +0100 - Daniele Nicolodi:
>On Tue, Mar 02, 2004 at 07:28:48PM +0100, terry@eatoni.com wrote:
[...]
>> What you have right now is expanding into something with two slashes
>> in it (${R}/trunk expands to http://localhost:8080/svn/code//trunk for
>> example).
>
>Yes, i know. My report is about svn not working right with urls that
>contains a repeated path separator (//). Any unix program interpretes
>a double path separator (//) like it is a single one (/) and the same
>is done for urls. I don't know if this is covered by RFC and if so what
>RFC says but i think that, for coerence, // should be handled like /.

An example of widespread appliaction that doesnt work like that is
Emacs (yeah, vi is also widespread). If you open a file (find-file)
and type a second / it refers to the root directory. Similarly
/tmp/~/.emacs refers to $HOME/.emacs. Perhaps thats not common for
other applications, I dont know.

.h

-- 
Henrik Holmboe, Stockholm, Sweden
<http://henrik.holmboe.se/contact/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org