deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

example conf: clarify group name parsing

Browse source
This commit is contained in:
Sitaram Chamarty 2009-11-30 07:00:31 +05:30
parent 81911b77cc
commit bfc3b6cd58
1 changed files with 12 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
conf/example.conf
View file

@ -24,9 +24,13 @@
# syntax: # syntax:
# @groupname = [one or more names] # @groupname = [one or more names]
# groups let you club names together for convenience in specifying # groups let you club (user or group) names together for convenience
# permissions. A group is simply expanded to whatever names are on the right
# hand side when it is actually used # * a group is like a #define in C except that it can *accumulate* values
# * the config file is parsed in a single-pass, so later *additions* to a
# group name cannot affect earlier *uses* of it
# The following examples should illustrate all this:
# you can have a group of people... # you can have a group of people...
@staff = sitaram some_dev another-dev @staff = sitaram some_dev another-dev
@ -43,10 +47,14 @@
@staff = au.thor @staff = au.thor
# so now "@staff" expands to all 4 names # so now "@staff" expands to all 4 names
# groups can include other groups (but not recursively) # groups can include other groups, and the included group will
# be expanded to whatever value it currently has
@interns = indy james @interns = indy james
@staff = bob @interns @staff = bob @interns
# "@staff" expands to 7 names now # "@staff" expands to 7 names now
@interns = han
# "@interns" now has 3 names in it, but note that this does
# not change @staff
# REPO AND BRANCH PERMISSIONS # REPO AND BRANCH PERMISSIONS
# --------------------------- # ---------------------------