README: expand the Where To Send Patches section
PATCH 1/1 README: expand the Where To Send Patches section
Signed-off-by Ross Burton <[email protected]>
--- README | 27 ++++++++++++++++++--------- 1 file changed, 18 insertions(+), 9 deletions(-)
README +18 -9
@@ -30,20 +30,29 @@ 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. +As Poky is an integration repository (built using a tool called combo-layer), +patches against the various components should be sent to their respective +upstreams: bitbake: - [email protected] + Git repository: http://git.openembedded.org/bitbake/ + Mailing list: [email protected] -meta-yocto: +documentation: + Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/ + Mailing list: [email protected] + +meta-yocto(-bsp): + Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp) [email protected] -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. +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 repository. - [email protected] -Note: The scripts directory should be treated with extra care as it is a mix - of oe-core and poky-specific files. + Git repository: http://git.openembedded.org/openembedded-core/ + Mailing list: [email protected] + +Note: The scripts directory should be treated with extra care as it is a mix of +oe-core and poky-specific files.
Signature · 1 line
1.7.10.4