Mirror of git.openembedded.org/meta-openembedded https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=master 2013-09-03T17:12:37+00:00 2013-09-03T17:12:37+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2013-08-28T10:43:25+00:00 urn:sha1:6f642a51dc98b0a8a20b2d0a6bfe6917e9f2091f This is now in OE-Core as of 807285c751862aaa775db5a13293007bfb3c29df. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> 2013-04-15T14:23:17+00:00 Martin Jansa Martin.Jansa@gmail.com 2013-04-13T20:49:41+00:00 urn:sha1:a45830a39bb47a9eab27980d52966226c9504ea4 * 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-04-16T11:50:43+00:00 Martin Jansa Martin.Jansa@gmail.com 2011-04-15T16:12:37+00:00 urn:sha1:dc4339fae98fa38dfee39b74f52ba7407e600809 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>