meta-openembedded/meta-oe
Koen Kooi cbcf7323bf asio 1.4.1: import from OE classic
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
2011-10-24 16:24:25 +02:00
..
classes glx-use-tls: moved to oe-core with mesa recipes 2011-10-12 20:28:34 +02:00
conf machine includes: remove from layer 2011-05-25 16:05:04 +02:00
recipes-benchmark memtester: Import from OE classic 2011-10-24 08:41:43 +02:00
recipes-connectivity soft66 git: import from OE classic 2011-10-24 16:24:25 +02:00
recipes-core udev 174: add version 174, disabled by default (see below) 2011-10-24 16:24:25 +02:00
recipes-devtools cloud9 0.5.1: fix up node-o3-xml library location 2011-10-24 11:36:55 +02:00
recipes-extended subsurface: update to 1.1 release, start using gitpkgv 2011-10-24 16:24:20 +02:00
recipes-gnome/gtk+ gtkmm: add 2.20.0 2011-07-12 12:25:24 +02:00
recipes-graphics pixman 0.23.6: apply typo fix from upstream 2011-10-19 09:30:51 +02:00
recipes-kernel/kexec kexec-tools: add bbappend to keep old packaging with separate kexec and kdump 2011-08-18 10:52:05 +02:00
recipes-multimedia live555: fix build due to missing INC_PR 2011-10-24 16:24:22 +02:00
recipes-navigation recipes: use allarch instead of PACKAGE_ARCH = all 2011-10-12 10:24:45 +02:00
recipes-qt qt4: update to 4.7.4 2011-10-04 12:58:55 +02:00
recipes-support asio 1.4.1: import from OE classic 2011-10-24 16:24:25 +02: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>