From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libsdl-native: Convert to new style staging, remove do_stage
Date: Tue, 07 Sep 2010 07:32:50 +0100 [thread overview]
Message-ID: <4C85DC92.2070002@xora.org.uk> (raw)
In-Reply-To: <AANLkTimxy+r7_Wgaq1SvmWHBPRuvZ+Wtvn1Ctm=maaGb@mail.gmail.com>
On 07/09/10 07:32, Frans Meulenbroeks wrote:
> 2010/9/7 Graham Gower <graham.gower@gmail.com>:
>> On 6 September 2010 21:49, Noor Ahsan <noor_ahsan@mentor.com> wrote:
>>> * Remove do_stage ()
>>> * Replace tabs with 8 spaces in do_configure
>> I see that spaces and not tabs are the OE policy, but I can't lay my
>> eyes on anything that says how many spaces are preferred. I see a lot
>> of recipes and examples using 4 space indentation (and most others use
>> a tab). Is this something that people care about?
>>
>> -Graham
>>
>> PS: Personally I'm a tab man, not a spaceman.
> Afaik it is not defined.
> There is http://wiki.openembedded.net/index.php/Styleguide
> which only says "#
> # Use spaces for indentation as developers tends to use different
> amount of spaces per one tab. "
> now we're just using a different amount of spaces :-)
>
> (actually using different # of spaces for a tab is not that bad as
> long as you stick to tabs only. That is why the linux kernel requires
> indentig by tabs).
>
> Frans (who also likes tabs, if only because it is the default in vi
> with autoindent (and yeah, I know you can change that))
>
Informally the policy has always been we dont care tabs or spaces as
long as its consistent within the same recipe.
Graeme
prev parent reply other threads:[~2010-09-07 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 12:19 [PATCH] libsdl-native: Convert to new style staging, remove do_stage Noor Ahsan
2010-09-06 12:34 ` Frans Meulenbroeks
2010-09-06 12:38 ` Ahsan, Noor
2010-09-06 23:27 ` Graham Gower
2010-09-07 6:32 ` Frans Meulenbroeks
2010-09-07 6:32 ` Graeme Gregory [this message]
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=4C85DC92.2070002@xora.org.uk \
--to=dp@xora.org.uk \
--cc=openembedded-devel@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.