documentation: Elaborate on branch level Owner

We now support branch level ownership, so describe a case of that
in the Owner category section.

Change-Id: I55bada3d07a060f30deb6afaf9ccb2249e1e944b
Signed-off-by: Shawn O. Pearce <sop@google.com>
This commit is contained in:
Shawn O. Pearce
2010-04-27 14:14:10 -07:00
parent d22eabcb3c
commit da69f86d40

View File

@@ -216,6 +216,13 @@ through the web UI, but not through SSH. To get SSH branch access
project owners must grant an access right to a group they are a project owners must grant an access right to a group they are a
member of, just like for any other user. member of, just like for any other user.
Ownership over a particular branch subspace may be delegated by
entering a branch pattern. To delegate control over all branches
that begin with `qa/` to the QA group, add `Owner` category
for reference `refs/heads/qa/\*`. Members of the QA group can
further refine access, but only for references that begin with
`refs/heads/qa/`.
[[category_READ]] [[category_READ]]
Read Access Read Access
~~~~~~~~~~~ ~~~~~~~~~~~