OpenEmbedded welcomes contributions. Before submitting a patch however there are a few things to keep in mind.

−

'''Note''': More details are available on the policy pages, but this document is good enough for most beginners.

+

== Finding the right place for your patch ==

−

* [[Patchwork]]

+

OpenEmbedded is now split up into separate layers: OpenEmbedded-Core (OE-Core) which is a small set of core recipes, and other layers for recipes beyond that. For most layers, patches are sent to a mailing list for review before being merged. Further information specific to the layer you're working on please see the README file in the layer.

−

* [[Commit Policy]]

+

+

New recipes in particular should be added to the appropriate layer. See the [http://layers.openembedded.org layer index] for the list of public layers. If your new recipe doesn't seem to fit anywhere it can be added to the meta-oe layer in the meta-openembedded repository, although if it is likely to be followed by numbers of similar recipes then you may wish to consider creating a new layer.

+

+

== A task-oriented guide to creating a patch ==

−

Let's say you [[How to create a bitbake recipe for dummies|create a new bitbake recipe for OpenEmbedded]] and you'd like to submit it for inclusion (and you've already tested that it works, of course).

+

Let's say you have made a fix to a recipe, you've tested that it works and you'd like to submit it for merging.

You can use the --envelope-sender option to have the email appear from the address you are subscribed to the list with. You will need to use the Accounts and import tab under the gmail settings tab. Use the Send mail as selection to address you want to send email from.

−

1. Commit with a concise and descriptive message - one that explains your changes in a way others get a short overview without

+

=== Subscribe to the mailing list ===

−

looking at the code.

+

−

cd org.openembedded.dev/ # or whereever you keep your clone of the repo

+

You need to subscribe to the appropriate mailing-list in order to be able to send your patch(es) there; for patches against OE-Core the mailing list is '''openembedded-core@lists.openembedded.org''' and for patches against meta-oe and many other layers the list is '''openembedded-devel@lists.openembedded.org'''. See [[Mailing lists]] for subscription and further details.

−

git add recipes/nodejs/

+

+

=== Committing your patch ===

+

+

Commit with a concise and descriptive message - one that explains your changes in a way others get a short overview without looking at the code.

4. Once your patch has been accepted or rejected, create an account and update the status to "accepted" or "rejected"

+

−

4++. If you get '''soft-rejected (a lot of feedback)''', you should make changes according to the feedback, submit the next version, and update the status of the previous patch to "superseded". Remember to use `--subject-prefix` to mark the patch iteration.

+

For multiple commits you can substitute -1 above with -N (where N is the number of commits) or instead specify a revision before which to start e.g. HEAD~3, master etc.

+

+

Note: in either case if you are submitting a patch for meta-oe or any layer other than OE-Core, please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:

+

--subject-prefix="meta-oe][PATCH"

+

+

Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)

+

+

==== Sending via a pull request ====

+

+

Alternatively, for larger patch series it is preferable to send a pull request. This involves making a local branch on top of the master branch for your changes, pushing this branch to an accessible repository and then using the create-pull-request and send-pull-request scripts to create and send a patch series with a link to the branch for review.

+

+

Run scripts/create-pull-request and scripts/send-pull-request to get help on how to use these.

Your patch will be sent to the mailing list and should be immediately visible on http://patches.openembedded.org/

+

+

If you get feedback in reply to your patch, you should make changes according to the feedback and submit the next version. Please remember to use <code>--subject-prefix="PATCH v2"</code>, v3, v4 etc. to mark the patch iteration.

+

+

If your patch has not had any feedback after a few days it may have been missed or the appropriate reviewers may not currently be around; it is perfectly fine to reply to it yourself with a "ping" / reminder request for feedback.

== Appendix ==

== Appendix ==

−

=== steps for people which don't have snmp access for git ===

+

=== Steps for people which don't have SMTP access for git ===

−

Patches should not be set as attachment but inline.

+

Patches should not be sent as attachment but inline.

−

If you do not have snmp access to your email account you have two options:

+

If you do not have SMTP access to your email account you have two options:

−

1. use a different account (e.g. gmail). you can make one especially

+

1. Use a different account (e.g. gmail). you can make one especially for this. Note that the account may differ from the one in signed-off (although that is inconvenient)

−

for this. Note that the account may differ from the one in signed-off

+

−

(although that is inconvenient)

+

−

2. just include the patch in the body of your email. Make sure you use

+

2. Just include the patch in the body of your email. Make sure you use an email client that does not touch the message (turn spaces in tabs,

−

an email client that does not touch the message (turn spaces in tabs,

+

wrap lines etc etc).

wrap lines etc etc).

−

A good mail client to do so is '''pine''' (or '''alpine''')

+

A good mail client to do so is '''pine''' (or '''alpine''') or '''mutt'''. For more information refer to [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/email-clients.txt Documentation/email-clients.txt] in linux

+

kernel sources.

+

+

[[Category:FAQ]]

+

[[Category:User]]

Revision as of 08:51, 10 April 2013

OpenEmbedded welcomes contributions. Before submitting a patch however there are a few things to keep in mind.

Finding the right place for your patch

OpenEmbedded is now split up into separate layers: OpenEmbedded-Core (OE-Core) which is a small set of core recipes, and other layers for recipes beyond that. For most layers, patches are sent to a mailing list for review before being merged. Further information specific to the layer you're working on please see the README file in the layer.

New recipes in particular should be added to the appropriate layer. See the layer index for the list of public layers. If your new recipe doesn't seem to fit anywhere it can be added to the meta-oe layer in the meta-openembedded repository, although if it is likely to be followed by numbers of similar recipes then you may wish to consider creating a new layer.

A task-oriented guide to creating a patch

Let's say you have made a fix to a recipe, you've tested that it works and you'd like to submit it for merging.

You can use the --envelope-sender option to have the email appear from the address you are subscribed to the list with. You will need to use the Accounts and import tab under the gmail settings tab. Use the Send mail as selection to address you want to send email from.

Subscribe to the mailing list

You need to subscribe to the appropriate mailing-list in order to be able to send your patch(es) there; for patches against OE-Core the mailing list is openembedded-core@lists.openembedded.org and for patches against meta-oe and many other layers the list is openembedded-devel@lists.openembedded.org. See Mailing lists for subscription and further details.

Committing your patch

Commit with a concise and descriptive message - one that explains your changes in a way others get a short overview without looking at the code.

Sending using git-send-email

For multiple commits you can substitute -1 above with -N (where N is the number of commits) or instead specify a revision before which to start e.g. HEAD~3, master etc.

Note: in either case if you are submitting a patch for meta-oe or any layer other than OE-Core, please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:

--subject-prefix="meta-oe][PATCH"

Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)

Sending via a pull request

Alternatively, for larger patch series it is preferable to send a pull request. This involves making a local branch on top of the master branch for your changes, pushing this branch to an accessible repository and then using the create-pull-request and send-pull-request scripts to create and send a patch series with a link to the branch for review.

Run scripts/create-pull-request and scripts/send-pull-request to get help on how to use these.

Community review

If you get feedback in reply to your patch, you should make changes according to the feedback and submit the next version. Please remember to use --subject-prefix="PATCH v2", v3, v4 etc. to mark the patch iteration.

If your patch has not had any feedback after a few days it may have been missed or the appropriate reviewers may not currently be around; it is perfectly fine to reply to it yourself with a "ping" / reminder request for feedback.

Appendix

Steps for people which don't have SMTP access for git

Patches should not be sent as attachment but inline.

If you do not have SMTP access to your email account you have two options:

1. Use a different account (e.g. gmail). you can make one especially for this. Note that the account may differ from the one in signed-off (although that is inconvenient)

2. Just include the patch in the body of your email. Make sure you use an email client that does not touch the message (turn spaces in tabs,
wrap lines etc etc).