Guidelines for contributing to meta-intel layer: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
No edit summary
Line 27: Line 27:
== Review process for sending commits and BSPs to meta-intel layer ==
== Review process for sending commits and BSPs to meta-intel layer ==
* All the commits for meta-intel layer must go through the meta-intel mailing list.
* All the commits for meta-intel layer must go through the meta-intel mailing list.
* The changes should be sent as individual commits. There is a specific way to send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change  
* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change  
* Do not send tarballs of code for review.
* Do not send tarballs of code for review.

Revision as of 00:11, 25 October 2013

meta-intel Layer Details

git repository:

Mailing List:


Guidelines for sending commits to meta-intel

Please follow general guidelines for contributing to Yocto Project. Here are some of the links.


Guidelines for submitting BSPs to meta-intel

1st follow these general BSP developer's guides:


Review process for sending commits and BSPs to meta-intel layer