From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: different access rights for oe branches?
Date: Thu, 10 Feb 2011 09:25:48 -0800 [thread overview]
Message-ID: <AANLkTi=c9c_ctv03Oe9f_2KAJ-eV4qNSkfAvwDh+ek97@mail.gmail.com> (raw)
In-Reply-To: <4D53E971.5090109@dresearch.de>
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
>
prev parent reply other threads:[~2011-02-10 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=c9c_ctv03Oe9f_2KAJ-eV4qNSkfAvwDh+ek97@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.