"SteveKing" wrote:
> > Looks like the path is being parsed and 'cleaned up' multiple times.
>
> Yes. TSVN allows you to enter non-URI-encoded URL's as you can in your
> browser. TSVN then does the encoding itself.
> When you enter file:///%5cserve/share/repos in the command line client,
> you 'trick' it by not specifying the '\' directly as you should be able
> to do, and the CL client then doesn't any encodings anymore. But that
> also means that e.g.
> file:///%5cserve/share with spaces/repos won't work anymore, then you
> have to use
> file:///%5cserve/share%20with%20spaces/repos
> for it to work, which you wouldn't have if the UNC share paths would
> actually work in Subversion.
That's not true in SVN 1.1.0. I can do these illegal things now:
svn ls file:///\serve\share with spaces\repos
svn ls file:///%5cserve\share with spaces/repos
The new SVN parsing seems to accept backslashes and slashes (almost)
interchangeably, except for that leading backslash on a UNC path. I'm not
saying SVN is correct, just that it is more tolerant as well as being broken
;-/
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Oct 1 11:45:21 2004