139c08d3a1
(and the other Dan Carpenter finding too, while we're about it!) Note that neither of these is an actual issue, (and even less likely now that gitolite is pure perl and no shell metas used) but it's just playing safe. |
||
---|---|---|
.. | ||
keys | ||
0-me-first.t | ||
access.t | ||
all-yall.t | ||
basic.t | ||
branch-perms.t | ||
deleg-1.t | ||
deleg-2.t | ||
deny-create.t | ||
deny-rules-2.t | ||
deny-rules.t | ||
git-config.t | ||
gitolite-receive-pack | ||
gitolite-upload-pack | ||
glt | ||
include-subconf.t | ||
info.t | ||
invalid-refnames-filenames.t | ||
listers.t | ||
merge-check.t | ||
perm-roles.t | ||
perms-groups.t | ||
personal-branches.t | ||
README | ||
reset | ||
rule-seq.t | ||
sequence.t | ||
ssh-authkeys.t | ||
ssh-basic.t | ||
vrefs-1.t | ||
vrefs-2.t | ||
wild-1.t | ||
wild-2.t | ||
writes.t | ||
z-end.t |
WARNING: THE TEST SUITE DELETES STUFF FIRST! Testing gitolite3 is now one command after the clone: prove But because it starts by cleaning the slate, it's best to do it on a spare userid that you are ok to lose data on.