From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Michael Halstead <michael@yoctoproject.org>
Cc: toaster@yoctoproject.org
Subject: Re: Poky-contrib access
Date: Wed, 08 Jan 2014 23:29:20 +0000 [thread overview]
Message-ID: <2843704.O78OJRlBgx@helios> (raw)
In-Reply-To: <52CDAC7F.5030002@yoctoproject.org>
Hi Michael,
On Wednesday 08 January 2014 11:52:31 Michael Halstead wrote:
> On 01/08/2014 10:41 AM, Paul Eggleton wrote:
> > Hi folks,
> >
> > As we've talked about, in order to contribute to Toaster, you really need
> > to get push access to the poky-contrib repository so you can push your
> > own branches there for people to review. In order to do that, you need
> > to:
> >
> > 1) If you haven't already, generate an SSH key pair on your machine
> >
> > 2) Send a request for push access to poky-contrib with the *public* key
> > attached to Michael Halstead <michael@yoctoproject.org>
>
> Please include your intended branch prefix when sending your public key.
> In my case it would be halstead because my branches are all named
> halstead/<topic>.
OK, thanks, I wasn't aware of that.
> > 3) Once Michael has added your key, either:
> >
> > a) Add poky-contrib as a remote:
> > git add poky-contrib ssh://git@git.yoctoproject.org/poky-contrib
>
> Also you'll need to use "remote add". Note that the username when
> pushing to git.yoctoproject.org is always git.
>
> git remote add poky-contrib ssh://git@git.yoctoproject.org/poky-contrib
Oops, mistake on my part. I definitely meant "git remote add" and not "git
add".
(I guess we should probably add all of this stuff to a wiki page somewhere, if
we don't already have it.)
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2014-01-08 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 18:41 Poky-contrib access Paul Eggleton
2014-01-08 18:46 ` Paul Eggleton
2014-01-08 19:52 ` Michael Halstead
2014-01-08 23:29 ` Paul Eggleton [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=2843704.O78OJRlBgx@helios \
--to=paul.eggleton@linux.intel.com \
--cc=michael@yoctoproject.org \
--cc=toaster@yoctoproject.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.