[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "svn commit" does not work with SVNParentPath in location and 1.7-client (HTTPv2)

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Thu, 17 Nov 2011 11:50:20 +0000

Stefan Sperling <stsp_at_elego.de> writes:

> How do we avoid ambiguity when handling requests to nested Locations?
> How can a client access a folder /bar inside a repository at Location /svn
> if another repository exists at a nested Location /svn/bar?

Yes, I was surprised too! If we assume that /svn and /svn/foo are
directories that contain repositories then there can be no overlap:

<Location /svn>
  SVNParentPath /svn
<Location /svn/foo>
  SVNParentPath /svn/foo

/svn/repo/<something> and /svn/foo/repo/<something> cannot overlap.

The only way there could be a problem is if /svn/foo were itself a
repository, but the admin can ensure that is not the case.

Received on 2011-11-17 12:54:29 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.