[oe] Patch procedure for dummies

[Hauser, Wolfgang (external)]

Thanks from me too, but for me it would be helpful to add the necessary steps for people which don't have
snmp access for git and have to send patches through the allowed mail client as an attachment.

Regards
Wolfgang
 
-----Ursprüngliche Nachricht-----
Von: openembedded-devel-bounces at lists.openembedded.org [mailto:openembedded-devel-bounces at lists.openembedded.org] Im Auftrag von J. L. 
Gesendet: Mittwoch, 25. August 2010 19:47
An: openembedded-devel at lists.openembedded.org
Betreff: Re: [oe] Patch procedure for dummies

A huge thanks for taking the time AJ keep you the great work, I am
sure your helping tons of people me included!




On Wed, Aug 25, 2010 at 7:43 AM, AJ ONeal <coolaj86 at gmail.com> wrote:
> Please give me feedback and I'll post this on the wiki.
>
> A task-oriented guide to creating a patch:
>
>
>
>> Let's say you create a new recipe and you'd like to submit it for inclusion
>> (and you've already tested that it works, of course).
>>
>> 1. Now commit with a good strong helpful message
>>
>>     git add recipes/nodejs/
>>     git commit # don't use the -m option
>>
>> 2. The message should look like this
>>
>>     added recipe for node.js
>>
>>     * added recipe for node.js (bug #5555 - no nodejs recipe)
>>     ** patched libev's wscript to not try to execute code
>>     ** patched node's wscript to not search in '/usr/include'
>>
>>     Signed-off-by: AJ ONeal <coolaj86 at gmail.com>
>>
>> 3. Create your patch
>>
>>     git format-patch -1 # or however many commits are part of this change
>>
>> 3++. If you are submitting a second version also add "--subject-prefix
>> [v2]"
>>
>>     git send-email
>>
>> Your patch will be immediately visible on
>> http://patchwork.openembedded.org/patch/
>>
>
>
>> 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), make the changes, submit
>> the next version, and update the status of the previous patch to
>> "superseded"
>>
>> Appendix: Properly configuring git (using tekkub at gmail.com as an example
>> user)
>>
>>     sudo apt-get install git-core git-email
>>     git config --global user.name "Tekkub"
>>     git config --global user.email "tekkub at gmail.com"
>>     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 at gmail.com
>>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel at lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel