README: Clarify where to send patches

There is still a great deal of confusion over where patches for the
various components of the poky repository should be sent. Attempt to
mitigate this by including a blurb in the poky README similar to what
other layers and repositories do.

V2: Call out the special care required when dealing with the scripts
    directory per Saul Wold's recommendation.

V3: Recommend applying patches to oe-core prior to sending patches to
    the oe-core mailing list.

(From meta-yocto rev: d2747240e75ca0d43f569161694799c3d5d23014)

Signed-off-by: Darren Hart <>
CC: Richard Purdie <>
CC: Paul Gortmaker <>
CC: Paul Eggleton <>
CC: Khem Raj <>
Signed-off-by: Richard Purdie <>
Darren Hart 2012-08-21 09:27:16 -07:00 committed by Richard Purdie
parent a0a3a44240
commit d15f126501
1 changed files with 20 additions and 0 deletions

View File

@ -27,3 +27,23 @@ DISTRO = "") and contains only emulated machine support.
For information about OpenEmbedded, see the OpenEmbedded website:
Where to Send Patches
As Poky is an integration repository, patches against the various components
should be sent to their respective upstreams.
Most everything else should be sent to the OpenEmbedded Core mailing list. If
in doubt, check the oe-core git repository for the content you intend to modify.
Before sending, be sure the patches apply cleanly to the current oe-core git
Note: The scripts directory should be treated with extra care as it is a mix
of oe-core and poky-specific files.