All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: how do I contribute to yocto
Date: Mon, 20 Feb 2012 10:24:08 -0800	[thread overview]
Message-ID: <4F428FC8.5080806@intel.com> (raw)
In-Reply-To: <1329746626.2728.10.camel@babel.joshhome>

On 02/20/2012 06:03 AM, Joshua Immanuel wrote:
> Hello all,
> 	In the process of creating my custom image, I ended up writing new
> recipes for packages which does not exist in yocto. I think it will be
> useful for others. I use the edison branch for my work, and I add the
> new recipes to my custom layer without disturbing the edison branch. So,
> how do I contribute these new recipes?
>
> Read the wiki https://wiki.yoctoproject.org/wiki/Contribution_Guidelines
> it doesn't mention about the branch to use etc.
>
> Can someone guide me.

Hi Joshua,

I'd put your layer up on a git repo somewhere (GitHub?) and make sure 
you have a note in your layer's README file that mentions that the layer 
is intended for use with the edison release.

If you're looking to maintain this layer for multiple releases of Yocto, 
it may make sense to maintain a similar branch structure - i.e, your 
master branch aims to build with Poky master, edison branch builds with 
edison, etc.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center


  reply	other threads:[~2012-02-20 18:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 14:03 how do I contribute to yocto Joshua Immanuel
2012-02-20 18:24 ` Scott Garman [this message]
2012-02-21  5:40   ` Joshua Immanuel
2012-02-21  6:12     ` Khem Raj
2012-02-21  6:22       ` Joshua Immanuel
2012-02-22 15:49   ` Bob Cochran
2012-02-22 16:47     ` 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=4F428FC8.5080806@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=yocto@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.