Difference between revisions of "Submit patches to Openembedded"
(→Submit patches to Openembedded (core)) |
(→Set up git) |
||
Line 5: | Line 5: | ||
=== Set up git === | === Set up git === | ||
− | + | In this case I have a subscribed the oopenembedded-devel mailing list with a gmail.com account and I sign my patch with another account. | |
− | |||
Properly configuring git (using tekkub@gmail.com as an example user) | Properly configuring git (using tekkub@gmail.com as an example user) | ||
Line 15: | Line 14: | ||
These are important to the commit meta-data | These are important to the commit meta-data | ||
− | git config --global user.name " | + | git config --global user.name "Myself Me" |
− | git config --global user.email " | + | git config --global user.email "myname@mydomain.com" |
Any Google Apps account | Any Google Apps account |
Revision as of 13:22, 7 January 2013
Contents
Submit patches to Openembedded (core)
Submitting patches to oe-core is slightly different than what was used with oe-classic. You can read the official [Openembedded howto]
Set up git
In this case I have a subscribed the oopenembedded-devel mailing list with a gmail.com account and I sign my patch with another account. Properly configuring git (using tekkub@gmail.com as an example user)
On Debian / Ubuntu (Note: Fedora uses `yum` OpenSuse uses zypper or yast)
sudo aptitude install git-core git-email
These are important to the commit meta-data
git config --global user.name "Myself Me" git config --global user.email "myname@mydomain.com"
Any Google Apps account
git config --global sendemail.smtpserver smtp.gmail.com git config --global sendemail.smtpserverport 587 git config --global sendemail.smtpencryption tls git config --global sendemail.smtpuser tekkupl@gmail.com
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.
Move to oe-core directory or whereever you keep your clone of the repo
cd oe-core
Add the modified file
git add path/recipename
Add a comment including my signature "Signed-off-by: Your Name <name@domain.com>"
git commit -s recipename: brief description * Longer description * if * required
Please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:
git format-patch -s --subject-prefix="oe][meta-oe][PATCH" -1
Sending using git-send-email
To send just the top commit on your current branch (substitute mailing list address as appropriate):
git send-email --to=openembedded-core@lists.openembedded.org --confirm=always -M -1