Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Chris Larson <clarson@kergoth.com>
Subject: Re: Yocto style guide change proposal
Date: Fri, 20 Jul 2012 17:07:09 +0200	[thread overview]
Message-ID: <20120720150709.GG3534@jama.jama.net> (raw)
In-Reply-To: <4851908.FI1zozqsjq@helios>

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

On Fri, Jul 20, 2012 at 03:31:04PM +0100, Paul Eggleton wrote:
> On Friday 20 July 2012 07:15:28 Chris Larson wrote:
> > If you don't see two different types of indentation in one file as
> > inconsistent, I think you need to look up consistency in a dictionary.
> 
> You're not wrong - but that's not the point. Personally I'd really prefer we 
> had four spaces everywhere; I'm not entirely sure why we chose this convention 
> in the first place. However, it's the convention we have now and changing it 
> has serious implications - almost every recipe will have to be changed; 

It doesn't need to be changed now everywhere, recipe maintainers can
change it if they want e.g. when upgrading recipe (preferably in
separate commit). Tabs highlight will help with that..

> backporting changes to stable releases will be made more difficult; submitted 
> patches crossing the switch will be difficult to apply, history will be 
> polluted, etc.
> 
> Changing this is not a small undertaking.

meta-efl + meta-smartphone size is about 1/2 of oe-core (counting .bb +
.inc) and it took only about 1 hour to replace all tabs with 8 spaces 
(when it was used to indent e.g. SRC_URI) or 4 spaces (when it was used 
in shell functions).

In many cases I had to replace 8 spaces with 4 when those shell
functions were indented with spaces already or with tabs/spaces mix.

Yes it's only aesthetics, but that's what "style guide" usually does.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2012-07-20 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20  9:32 Yocto style guide change proposal Martin Jansa
2012-07-20 13:56 ` Richard Purdie
2012-07-20 13:57   ` Chris Larson
2012-07-20 14:12     ` Richard Purdie
2012-07-20 14:15       ` Chris Larson
2012-07-20 14:31         ` Paul Eggleton
2012-07-20 15:07           ` Martin Jansa [this message]
2012-07-20 15:17   ` Martin Jansa
2012-07-20 15:46     ` Richard Purdie

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=20120720150709.GG3534@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=clarson@kergoth.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox