From: Trevor Woerner <trevor.woerner@linaro.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: unmaintained layers
Date: Thu, 09 Jan 2014 13:45:23 -0500 [thread overview]
Message-ID: <52CEEE43.1090209@linaro.org> (raw)
Hi everyone,
At the last TSC meeting the topic of unmaintained layers came up. Here
is the sorted list of master layers from the layer index [1], would it
be possible for those in the know to indicate which layers are, or are
suspected of being, unmaintained?
meta-aarch64
meta-acer
meta-ada
meta-android
meta-angstrom
meta-arago-distro
meta-arago-extras
meta-asus
meta-aurora
meta-baryon
meta-beagleboard
meta-beagleboard-extras
meta-browser
meta-bug
meta-buglabs
meta-chicken
meta-chiefriver
meta-clutter
meta-crownbay
meta-crystalforest
meta-cubox
meta-darwin
meta-eca
meta-efikamx
meta-efl
meta-eldk
meta-emenlow
meta-erlang
meta-ettus
meta-filesystems
meta-fri2
meta-fsl-arm
meta-fsl-arm-extra
meta-fsl-demos
meta-fsl-ppc
meta-fso
meta-games
meta-geeksphone
meta-gir
meta-gnome
meta-gpe
meta-gstreamer10
meta-guacamayo
meta-gumstix
meta-gumstix-community
meta-gumstix-extras
meta-hamradio
meta-handheld
meta-hipos
meta-htc
meta-igep
meta-initramfs
meta-intel
meta-ivi
meta-jasperforest
meta-java
meta-kde
meta-kernel-dev
meta-kirkwood
meta-linaro
meta-linaro-toolchain
meta-lsi
meta-lxcbench
meta-measured
meta-mentor
meta-micro
meta-mingw
meta-minnow
meta-mono
meta-multimedia
meta-n450
meta-netbookpro
meta-netmodule
meta-networking
meta-nokia
meta-nslu2
meta-nuc
meta-oe
meta-openmoko
meta-openpandora
meta-openstack
meta-openstack-compute-deploy
meta-openstack-controller-deploy
meta-openstack-qemu
meta-opie
meta-oracle-java
meta-osmocombb
meta-ouya
meta-palm
meta-perl
meta-picosam9
meta-qt3
meta-qt5
meta-raspberrypi
meta-realtime
meta-ro-rootfs
meta-romley
meta-ros
meta-ruby
meta-samsung
meta-sdr
meta-security
meta-selinux
meta-shr
meta-shr-distro
meta-slugos
meta-smalltalk
meta-sourcery
meta-sugarbay
meta-sunxi
meta-sys940x
meta-systemd
meta-telephony
meta-telldus
meta-ti
meta-tlk
meta-tracing
meta-virtualization
meta-web-kiosk
meta-webos
meta-webos-ports
meta-webserver
meta-woce
meta-x10
meta-xfce
meta-xilinx
meta-xilinx-community
meta-yassl
meta-yocto
meta-yocto-bsp
meta-zynq
meta-zynq-milo
openembedded-core
toolchain-layer
Thank you for your input, and best regards,
Trevor
[1] http://layers.openembedded.org/layerindex/branch/master/layers/
next reply other threads:[~2014-01-09 18:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 18:45 Trevor Woerner [this message]
2014-01-09 21:45 ` unmaintained layers Bruce Ashfield
2014-01-09 22:43 ` Mark Hatle
2014-01-09 23:20 ` Trevor Woerner
2014-01-10 1:14 ` Philip Balister
2014-01-10 4:54 ` Bruce Ashfield
2014-01-10 5:47 ` Marko Lindqvist
2014-01-09 23:35 ` Martin Jansa
2014-01-10 1:23 ` Chris Larson
2014-01-10 4:50 ` Bruce Ashfield
2014-01-10 5:54 ` Andreas Müller
2014-01-10 6:29 ` Nathan Rossi
2014-01-10 7:03 ` Fathi Boudra
2014-01-10 7:08 ` Lukas Bulwahn
2014-01-10 7:21 ` Hongxu Jia
2014-01-10 13:20 ` Mario Schuknecht
2014-01-10 14:01 ` Paul Eggleton
2014-01-10 15:35 ` Koen Kooi
2014-01-10 15:51 ` Trevor Woerner
2014-01-10 16:02 ` Philip Balister
2014-01-10 16:24 ` Trevor Woerner
2014-01-10 16:28 ` Saul Wold
2014-01-10 17:27 ` Andrei Gherzan
2014-01-10 18:54 ` João Henrique Freitas
2014-01-12 20:28 ` Mike Looijmans
2014-01-12 20:42 ` Trevor Woerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CEEE43.1090209@linaro.org \
--to=trevor.woerner@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.