https://bz.mercurial-scm.org/show_bug.cgi?id=5489

            Bug ID: 5489
           Summary: AclExtension: Support pattern matching for branch
                    rules
           Product: Mercurial
           Version: 3.9
          Hardware: PC
                OS: Windows
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: Mercurial
          Assignee: bugzi...@mercurial-scm.org
          Reporter: nikolaos.gki...@googlemail.com
                CC: mercurial-de...@selenic.com

This feature wish refers to the AclExtension. However, this extension does not
have an entry in the component list of this Bugzilla. I hope it assigning it to
the Mercurial component was right.

The "hg help acl" documentation states the following:

##################################################
#Branch-based Access Control
#---------------------------
#
#Use the "acl.deny.branches" and "acl.allow.branches" sections to have #branch-
#based access control. Keys in these sections can be either:
#
#- a branch name, or
#- an asterisk, to match any branch;
#
#The corresponding values can be either:
#
#- a comma-separated list containing users and groups, or
#- an asterisk, to match anyone;
#
#You can add the "!" prefix to a user or group name to invert the sense of #the
#match.
###################################################

The request is to implement simple pattern matching for the branch name. This
would enable you to set rules for a variable number of branches matching a
certain pattern. For example the hgrc entry could look like this:

##################################################
#[acl.allow.branches]
#release/* = @reviewers
##################################################

This example would allow the reviewers group only to do work on branches whose
name starts with "release/*".

A question regarding a feature like this one was posted to StackExchange in
2011 (http://superuser.com/questions/249453/mercurial-set-up-acl). It was
suggested to file a feature wish but I could not find one regarding this
feature. So here is mine. I hope it can be implemented. Thanks for your time!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Reply via email to