aboutsummaryrefslogtreecommitdiffstats
path: root/meta-efl/recipes-efl/e17/terminology.inc
AgeCommit message (Collapse)Author
2014-06-21terminology: upgrade to 0.5.1Martin Jansa
* announcement: https://phab.enlightenment.org/phame/post/view/57/ * LIC_FILES_CHKSUM change is just Copyright year update: < Copyright (C) 2012-2014 Carsten Haitzler and various contributors (see AUTHORS) --- > Copyright (C) 2012-2012 Carsten Haitzler and various contributors (see AUTHORS) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-02-23terminology: upgrade to 0.4.0Martin Jansa
* announcement http://sourceforge.net/mailarchive/message.php?msg_id=31728362 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-04-15recipes: Unify indentationMartin 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>
2012-09-05terminology: add version 0.1.0, negative D_P to svn and bump PEMartin Jansa
* PE bump is needed for upgrade path from svn recipe to 0.1.0 release Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>