meta-openembedded/meta-oe
2012-02-13 16:59:29 +01:00
..
classes systemd.bbclass: depends on systemd 2012-02-01 08:24:07 +01:00
conf machine includes: remove from layer 2011-05-25 16:05:04 +02:00
recipes-benchmark memtester: Corrected recipe following review comments and guidelines 2011-10-31 11:24:48 +01:00
recipes-connectivity dhcp: use PRINC 2012-02-06 13:27:34 +01:00
recipes-core recipes: bump PR to rebuild .la files without libz.la 2012-02-13 16:59:29 +01:00
recipes-devtools gdb-cross-canadian: drop .bbappned, doesn't work for me, fixed version sent to oe-core 2012-02-13 16:59:29 +01:00
recipes-extended recipes: bump PR to rebuild .la files without libz.la 2012-02-13 16:59:29 +01:00
recipes-gnome/gtk+ recipes: bump PR to rebuild .la files without libz.la 2012-02-13 16:59:29 +01:00
recipes-graphics recipes: bump PR to rebuild .la files without libz.la 2012-02-13 16:59:29 +01:00
recipes-kernel kexec-tools_2.0.2.bbappend: remove, packages are now split in oe-core 2012-01-11 09:28:26 +01:00
recipes-multimedia recipes: bump PR to rebuild .la files without libz.la 2012-02-13 16:59:29 +01:00
recipes-navigation gpsd: add systemd support 2012-01-23 16:23:12 +01:00
recipes-qt qt-4.8.0: enable sql features as in 4.7.4 2012-01-26 15:26:49 +01:00
recipes-support recipes: bump PR to rebuild .la files without libz.la 2012-02-13 16:59:29 +01:00
site rp-pppoe: Port from oe.dev 2011-07-26 21:51:39 +02:00
COPYING.MIT move layer into meta-oe in preparation for future splits 2011-03-17 21:41:22 +01:00
README README: add top level readme, update meta-oe one 2011-10-17 09:27:01 +02:00

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: master
revision: HEAD

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix meta-oe'

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.

Main layer maintainer: Koen Kooi <koen@dominion.thruhere.net>