From: Cliff Brake <cliff.brake@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Chris Larson <clarson@kergoth.com>
Subject: Re: different access rights for oe branches?
Date: Fri, 11 Feb 2011 11:58:30 -0500 [thread overview]
Message-ID: <AANLkTik6_nv73Bpf-21pKoDfYkKUSW4x9m-Xuyvg4Vis@mail.gmail.com> (raw)
In-Reply-To: <4D54FAA7.8030604@dresearch.de>
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
next prev parent reply other threads:[~2011-02-11 16:59 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 [this message]
2011-02-10 17:25 ` Khem Raj
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=AANLkTik6_nv73Bpf-21pKoDfYkKUSW4x9m-Xuyvg4Vis@mail.gmail.com \
--to=cliff.brake@gmail.com \
--cc=clarson@kergoth.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.