* different access rights for oe branches?
@ 2011-02-10 13:34 Steffen Sledz
2011-02-10 13:48 ` Chris Larson
2011-02-10 17:25 ` Khem Raj
0 siblings, 2 replies; 7+ messages in thread
From: Steffen Sledz @ 2011-02-10 13:34 UTC (permalink / raw)
To: openembedded-devel
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.
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: different access rights for oe branches?
2011-02-10 13:34 different access rights for oe branches? Steffen Sledz
@ 2011-02-10 13:48 ` Chris Larson
2011-02-10 13:55 ` Steffen Sledz
2011-02-10 17:25 ` Khem Raj
1 sibling, 1 reply; 7+ messages in thread
From: Chris Larson @ 2011-02-10 13:48 UTC (permalink / raw)
To: openembedded-devel
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.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: different access rights for oe branches?
2011-02-10 13:48 ` Chris Larson
@ 2011-02-10 13:55 ` Steffen Sledz
2011-02-10 17:22 ` Khem Raj
0 siblings, 1 reply; 7+ messages in thread
From: Steffen Sledz @ 2011-02-10 13:55 UTC (permalink / raw)
To: openembedded-devel; +Cc: Chris Larson
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?
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: different access rights for oe branches?
2011-02-10 13:55 ` Steffen Sledz
@ 2011-02-10 17:22 ` Khem Raj
2011-02-11 9:00 ` Steffen Sledz
0 siblings, 1 reply; 7+ messages in thread
From: Khem Raj @ 2011-02-10 17:22 UTC (permalink / raw)
To: openembedded-devel; +Cc: Chris Larson
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
>
> 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
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: different access rights for oe branches?
2011-02-10 17:22 ` Khem Raj
@ 2011-02-11 9:00 ` Steffen Sledz
2011-02-11 16:58 ` Cliff Brake
0 siblings, 1 reply; 7+ messages in thread
From: Steffen Sledz @ 2011-02-11 9:00 UTC (permalink / raw)
To: openembedded-devel; +Cc: Chris Larson
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: different access rights for oe branches?
2011-02-11 9:00 ` Steffen Sledz
@ 2011-02-11 16:58 ` Cliff Brake
0 siblings, 0 replies; 7+ messages in thread
From: Cliff Brake @ 2011-02-11 16:58 UTC (permalink / raw)
To: openembedded-devel; +Cc: Chris Larson
On Fri, Feb 11, 2011 at 4:00 AM, Steffen Sledz <sledz@dresearch.de> wrote:
> @admins: Please create a new branch named "hipox" by branching the "testing-release-2011.03" branch.
Done.
> @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.
Done, please test if possible (have other accounts try to push), and
let me know if anything is not working correctly.
You have re-wind permissions on this branch so you can back out commits, etc.
Cliff
--
=================
http://bec-systems.com
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: different access rights for oe branches?
2011-02-10 13:34 different access rights for oe branches? Steffen Sledz
2011-02-10 13:48 ` Chris Larson
@ 2011-02-10 17:25 ` Khem Raj
1 sibling, 0 replies; 7+ messages in thread
From: Khem Raj @ 2011-02-10 17:25 UTC (permalink / raw)
To: openembedded-devel
On Thu, Feb 10, 2011 at 5: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.
>
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.
> 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
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-02-11 16:59 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-10 13:34 different access rights for oe branches? Steffen Sledz
2011-02-10 13:48 ` Chris Larson
2011-02-10 13:55 ` Steffen Sledz
2011-02-10 17:22 ` Khem Raj
2011-02-11 9:00 ` Steffen Sledz
2011-02-11 16:58 ` Cliff Brake
2011-02-10 17:25 ` Khem Raj
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.