> Sorry to bother you again. It looks like you appended to patches in your > attachment. Please sent them separately. That doesn't matter, I am learning.
That doesn't matter, I am learning. But that are the things, a HowTo may contain and newbees don't know about w/o extensive manual digging. That HowTo could contain a step by step for creating a proper patch: 1. Changing code - references to "Best practices" 2. Checkout the proper base repository - commands - locations for http:// and git:// access 3. Commit the changes -commands (update/merge -> check in) -policies -commit message examples 4. Create a patch -commands -policies -background 5. Send a patch - commands - Subject examples - Header examples - Restrictions 6. Troubleshooting ... Just as an suggestion. Regards Wolfgang Hauser _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
