Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] base.bbclass: show layer's branches/revisions in the banner info
Date: Tue, 28 Jun 2011 16:24:37 +0100	[thread overview]
Message-ID: <1309274677.15156.170.camel@phil-desktop> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB6A167F0C716@shsmsx502.ccr.corp.intel.com>

On Tue, 2011-06-28 at 23:21 +0800, Cui, Dexuan wrote:
> Sorry... but to basing them on oe-core,  do I need the permission to push my commits to my own branch in git://git.openembedded.org/openembedded-core-contrib? I suppose so and I should put my public key somewhere into the server?

You don't need to do that.  You can just make a repo on github or
gitorious (or your own server, or even one of the yocto hosts) and clone
oe-core into it.

p.





  reply	other threads:[~2011-06-28 15:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28  5:37 [PATCH 0/1] base.bbclass: show layer's branches/revisions in the banner info Dexuan Cui
2011-06-28  5:37 ` [PATCH 1/1] " Dexuan Cui
2011-06-28  6:45   ` Koen Kooi
2011-06-28 11:07     ` Paul Eggleton
2011-06-29  1:01       ` Khem Raj
2011-06-29 16:14         ` Cui, Dexuan
2011-06-29 16:19           ` Koen Kooi
2011-06-29 16:44             ` Cui, Dexuan
2011-06-29 18:32               ` Khem Raj
2011-06-29 21:16               ` Koen Kooi
2011-06-28 14:27     ` Mark Hatle
2011-06-28 14:52       ` Cui, Dexuan
2011-06-28 15:10         ` Koen Kooi
2011-06-28 15:21           ` Cui, Dexuan
2011-06-28 15:24             ` Phil Blundell [this message]
2011-06-28 15:33             ` Mark Hatle
2011-06-28 15:45               ` Cui, Dexuan
2011-06-28 15:51               ` Koen Kooi
2011-06-28 15:13       ` Koen Kooi

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=1309274677.15156.170.camel@phil-desktop \
    --to=pb@pbcl.net \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox