Re: different access rights for oe branches?

[Steffen Sledz <sledz@dresearch.de>]

Am 10.02.2011 18:22, schrieb Khem Raj:
> On Thu, Feb 10, 2011 at 5:55 AM, Steffen Sledz <sledz@dresearch.de> wrote:
>> Am 10.02.2011 14:48, schrieb Chris Larson:
>>> On Thu, Feb 10, 2011 at 6:34 AM, Steffen Sledz <sledz@dresearch.de> wrote:
>>>> We like to create a branch specific for our hipox machine.
>>>>
>>>> Is it possible to define access rights different to the dev-branch here?
>>>>
>>>> We would like to give write access to some of our developers which do not have/need write access do dev. In opposite it would be nice to limit the write access to these maintainers.
>>>
>>> We use gitolite now, which can indeed exert control over branch access
>>> for the users, afaik.
>>
>> Fine. :)
>>
>> Who can setup these rights?
> 
> the admins :) create the branch and what sort of access control is
> required we can configure that

@admins: Please create a new branch named "hipox" by branching the "testing-release-2011.03" branch.

Am 10.02.2011 18:25, schrieb Khem Raj:
> well while its possible to give access to your developers I would
> suggest that this branch use a pull based approach where
> may be you maintain the branch and your devs submit the changes.

@khem: Please limit the write access to the new branch to me for the moment. May be we'll extend this to a few other developers/maintainers later.

Thanx,
Steffen

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@DResearch.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058