Latest commit b794949 Sep 8, 2016 @sitaramc fix 'access' command behaviour for 'C' and 'D' perms
Thanks to Alexander Groß for catching this.  Basically, the access command was
ignoring the presence or absence
Permalink
..
Failed to load latest commit information.
keys
0-me-first.t
C-vs-C.t
README
access.t
all-yall.t
basic.t
branch-perms.t
daemon-gitweb-via-perms.t
deleg-1.t
deleg-2.t
deny-create.t
deny-rules-2.t
deny-rules.t
easy.t
fork.t
git-config.t
gitolite-receive-pack
gitolite-upload-pack
glt
hostname.t
include-subconf.t
info-json.t
info.t
invalid-refnames-filenames.t
listers.t
merge-check.t
mirror-test
mirror-test-rc
mirror-test-setup.sh
mirror-test-ssh-config
partial-copy.t
perm-default-roles.t
perm-roles.t
perms-groups.t
personal-branches.t
reference.t
refex-expr-test-1
refex-expr-test-2
refex-expr-test-3
refex-expr-test-9
repo-specific-hooks.t
reset
rule-seq.t
sequence.t
smart-http
smart-http.root-setup
ssh-authkeys.t
ssh-basic.t
vrefs-1.t
vrefs-2.t
wild-1.t
wild-2.t
writable.t
z-end.t

README

============================================
WARNING: THE TEST SUITE DELETES STUFF FIRST!
============================================

Please run the tests ONLY on a userid where it's ok to LOSE DATA.

On such a userid, clone gitolite then run this command in the clone:

    GITOLITE_TEST=y prove

http://gitolite.com/gitolite/testing.html has more details.  Alternatively,
http://gitolite.com/gitolite/req.html#trying will help you try out gitolite if
you want to play with gitolite safely.