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

Re: svn commit: r1614080 - in /subversion/branches/authzperf: BRANCH-README subversion/libsvn_repos/authz.c subversion/libsvn_subr/config.c subversion/libsvn_subr/config_impl.h

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 29 Jul 2014 14:54:33 +0100

Branko Čibej <brane_at_wandisco.com> writes:

> Let's please have the rules documented in the wiki, then we can comment
> on them.
>> * Select the path rule(s) that cover the largest section of the path.
>> This is what we do today and there can be only one such match
>> w/o the use of wildcards.
>> * If there is more than one such rule, apply the one declared last.
>> This seems to be the easiest rule to follow and understand.
> Well, I disagree, I'd expect an exact match to override a wildcard match.

That seems reasonable but raises the expectation that there is a more
general order for wildcards. Given a path:


is either of the patterns:


an override for the pattern:



Does either of the patterns /A/*/*/D and /*/B/C/* override the other?

If we choose and release some simple wildcard behaviour how easy will it
be to implement more sophisticated behaviour in future releases?

Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2014-07-29 15:55:08 CEST

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

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