320356d66c
- a remote "id" (usually the IP) is generated and logged on the first log message in a "transaction" - speaking of which, a new "transaction ID" is logged that stays the same for each input command/invocation, tying together all the spawned commands - so now time stamps can be generated each time they are needed, rather than re-use the one at the beginning - log messages have a keyword at the start now remote, (create), check1 -- from gitolite-shell update, check2 -- from update post-up -- from post-update command -- from gitolite die, system -- from anywhere |
||
---|---|---|
.. | ||
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.