(rrq) document the report output

This commit is contained in:
Sitaram Chamarty 2010-04-24 15:46:25 +05:30
parent 08dced6125
commit 6edc7a4d5f
2 changed files with 17 additions and 32 deletions

View file

@ -408,20 +408,20 @@ etc. You'd just like a simple way to know what repos you have access to.
Easy! Just use ssh to give the "info" command to the gitolite server:
$ ssh git@server info
hello sitaram, the gitolite version here is v1.4-9-g34aad34
hello sitaram, the gitolite version here is v1.4.2-4-g40cbecd
the gitolite config gives you the following access:
R W SecureBrowse
R W anu-wsd
R W entrans
@ W git-notes
@ W gitolite
R W gitolite-admin
R W indic_web_input
@ R private/CREATER/[\w.-]+
R W proxy
@ @ W public/CREATER/[\w.-]+
@ @ testing
R W vkc
#R W SecureBrowse
#R W anu-wsd
#R W entrans
@R W git-notes
@R W gitolite
#R W gitolite-admin
#R W indic_web_input
@C #R private/CREATER/[\w.-]+
#R W proxy
@C @R W public/CREATER/[\w.-]+
@R @W testing
#R W vkc
To understand what these symbols mean, please see doc/report-output.mkd. The
administrator can also say things like:

View file

@ -22,17 +22,10 @@ can append a list of users to see their permissions instead of your own.
(Side note: if you installed using easy-install that would probably be `ssh
gitolite info`, by the way).
* col 1 (exists only if the "repo" name is actually a pattern)
* `@`: `@all` users have permission to create repos matching this
pattern
* `C`: this user has permission to create repos matching this pattern
* col 2
* `@`: `@all` users have read access to this repo
* `r`: this user has read access to `@all` repos
* `R`: this user has read access to this repo
* col 3: same as col 2, but for write access instead of read
The meaning of C, R, and W are self-explanatory, but they might sometimes be
prefixed by a symbol. For example, `@R` means that `@all` users have
beengiven this access, and `#R` means that this user is a "superuser" (think
root's shell prompt) and so has access to `@all` repos.
### the "expand" command
@ -51,11 +44,3 @@ account extra permissions enabled by the `setperms` command (see
doc/4-wildcard-repositories.mkd). It shows you the "creater" of the repo as
an additional column, defaulting to `<gitolite>` if it was not a wildcard
repo.
* col 1: not used
* col 2: same as col 2 for info, except substitute "repo" with "repo or
wildcard matching this repo"
* col 3: same as col 2, but for write access instead of read