From: Oleksandr Kravchuk <d...@sashko.rv.ua> Signed-off-by: Oleksandr Kravchuk <d...@sashko.rv.ua> --- meta-oe/README | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/meta-oe/README b/meta-oe/README index 7cde0a2da..db5697dd9 100644 --- a/meta-oe/README +++ b/meta-oe/README @@ -1,6 +1,9 @@ +meta-oe +======= + This layer depends on: -URI: git://github.com/openembedded/oe-core.git +URI: git://github.com/openembedded/openembedded-core.git branch: master revision: HEAD @@ -9,6 +12,11 @@ Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][PATCH' -You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI. +You are encouraged to fork the mirror on GitHub https://github.com/openembedded/openembedded-core +to share your patches, this is preferred for patch sets consisting of more than one patch. + +Other services like gitorious, repo.or.cz or self-hosted setups are of course accepted as well, +'git fetch <remote>' works the same on all of them. We recommend GitHub because it is free, easy +to use, has been proven to be reliable and has a really good web GUI. Main layer maintainer: Armin Kuster <akuster...@gmail.com> -- 2.17.1 -- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
