[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: Branko Čibej <brane_at_wandisco.com>
Date: Sat, 02 Aug 2014 16:45:44 +0200

On 02.08.2014 15:20, Alan Barrett wrote:
> On Tue, 29 Jul 2014, C. Michael Pilato wrote:
>> This leaves open the possibility of a future additional match mode for
>> regular expressions (using the '^:' magic prefix) should we seek to "go
>> there".
>> # Match the trunk and branches subdirs and their children.
>> [repos:^:^/(trunk|branches)(/.*|$)$]
> As a user, I'd prefer to see keywords rather than unusual characters
> to designate special syntax. For example, I would prefer
> [glob:/tags/*/private] and [regex:/tags/.*/private] to
> [*:/tags/*/private] and [^:/tags/.*/private].

Quite understood. Unfortunately, the syntax you propose above cannot
work; [thing:/path] is already a valid syntax, and if we did what you
propose, we'd no longer be able to create rules for repositories named
"glob" and "regex". Worse, this could change the meaning of existing
authz files.

We could do something like this, though:


In the old authz files, these rules would be invalid, because the
repository name part (the substring up to the first colon) cannot be empty.


-- Brane

Branko Čibej | Director of Subversion
WANdisco | Realising the impossibilities of Big Data
e. brane_at_wandisco.com
Received on 2014-08-02 16:46:14 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.