meta-openembedded-contrib - OpenEmbedded layers collection contribution trees

Age	Commit message (Collapse)	Author
2017-03-11	t1lib: Fix printf format string errors	Khem Raj
	Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2015-02-12	recipes: add x11 to required DISTRO_FEATURES	Martin Jansa
	Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-12-31	t1lib: Fix license format QA error	Otavio Salvador
	Fix following QA error: ,---- \| WARNING: Recipe t1lib, LICENSE (LGPLv2 GPLv2) has invalid format, \| LICENSES must have operator "([&\|() ])" between them. `---- Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-05-03	t1lib: Fix build when S != B	Khem Raj
	Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-02-23	recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issues	Matthieu CRAPET
	Changes: - rename SUMMARY with length > 80 to DESCRIPTION - rename DESCRIPTION with length < 80 to (non present tag) SUMMARY - drop final point character at the end of SUMMARY string - remove trailing whitespace of SUMMARY line Note: don't bump PR Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-04-15	recipes: Unify indentation	Martin Jansa
	* This change is only aesthetic (unlike indentation in Python tasks). * Some recipes were using tabs. * Some were using 8 spaces. * Some were using mix or different number of spaces. * Make them consistently use 4 spaces everywhere. * Yocto styleguide advises to use tabs (but the only reason to keep tabs is the need to update a lot of recipes). Lately this advice was also merged into the styleguide on the OE wiki. * Using 4 spaces in both types of tasks is better because it's less error prone when someone is not sure if e.g. do_generate_toolchain_file() is Python or shell task and also allows to highlight every tab used in .bb, .inc, .bbappend, .bbclass as potentially bad (shouldn't be used for indenting of multiline variable assignments and cannot be used for Python tasks). * Don't indent closing quote on multiline variables we're quite inconsistent wheater it's first character on line under opening quote or under first non-whitespace character in previous line. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Acked-by: Koen Kooi <koen@dominion.thruhere.net>
2011-11-21	t1lib: add 5.1.2	Koen Kooi
	Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>