From da69f86d40cff894cf9f0db34e421d3703dc760e Mon Sep 17 00:00:00 2001 From: "Shawn O. Pearce" Date: Tue, 27 Apr 2010 14:14:10 -0700 Subject: [PATCH] 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 --- Documentation/access-control.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/access-control.txt b/Documentation/access-control.txt index d6592c4ee1..45c8e9a3cb 100644 --- a/Documentation/access-control.txt +++ b/Documentation/access-control.txt @@ -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 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]] Read Access ~~~~~~~~~~~