git-svn: keep leading slash when canonicalizing paths (fallback case)
authorJonathan Nieder <jrnieder@gmail.com>
Fri, 5 Oct 2012 07:04:31 +0000 (00:04 -0700)
committerEric Wong <normalperson@yhbt.net>
Fri, 5 Oct 2012 22:52:52 +0000 (22:52 +0000)
Subversion's svn_dirent_canonicalize() and svn_path_canonicalize()
APIs keep a leading slash in the return value if one was present on
the argument, which can be useful since it allows relative and
absolute paths to be distinguished.

When git-svn's canonicalize_path() learned to use these functions if
available, its semantics changed in the corresponding way. Some new
callers rely on the leading slash --- for example, if the slash is
stripped out then _canonicalize_url_ourselves() will transform
"proto://host/path/to/resource" to "proto://hostpath/to/resource".

Unfortunately the fallback _canonicalize_path_ourselves(), used when
the appropriate SVN APIs are not usable, still follows the old
semantics, so if that code path is exercised then it breaks. Fix it
to follow the new convention.

Noticed by forcing the fallback on and running tests. Without this
patch, t9101.4 fails:

Bad URL passed to RA layer: Unable to open an ra_local session to \
URL: Local URL 'file://homejrnsrcgit-scratch/t/trash%20directory.\
t9101-git-svn-props/svnrepo' contains unsupported hostname at \
/home/jrn/src/git-scratch/perl/blib/lib/Git/SVN.pm line 148

With it, the git-svn tests pass again.

Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Eric Wong <normalperson@yhbt.net>
perl/Git/SVN/Utils.pm
index 4bb4dde89a3821ad7714c299b429f751cc98ebcc..8b8cf3755c268e03ef334534092bcd7959070cd2 100644 (file)
@@ -122,7 +122,6 @@ sub _canonicalize_path_ourselves {
        $path = _collapse_dotdot($path);
        $path =~ s#/$##g;
        $path =~ s#^\./## if $dot_slash_added;
-       $path =~ s#^/##;
        $path =~ s#^\.$##;
        return $path;
 }