From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] OpenEmbedded TSC 8 April 2013
Date: Wed, 24 Apr 2013 08:43:19 +0200 [thread overview]
Message-ID: <20130424064319.GD3217@jama> (raw)
In-Reply-To: <CA+YB3rb6xwk2-rsSa=dQx19qp7jKAVBZiMmQB5DvrGOmLUFG2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Tue, Apr 23, 2013 at 02:47:56PM -0700, Jeff Osier-Mixon wrote:
> OpenEmbedded Technical Steering Committee
> 8 April 2013
>
> b. document whitespace changes to the shell
> http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
> http://www.openembedded.org/wiki/Styleguide
> https://wiki.yoctoproject.org/wiki/Recipe_%26_Patch_Style_Guide
> => still need to de-dup these, need a volunteer
> ask for volunteers after 1.4 (jefro)
Someone probably noticed, but all meta-openembedded layers are now using
consistent indentation:
http://git.openembedded.org/meta-openembedded/commit/?id=a45830a39bb47a9eab27980d52966226c9504ea4
Can we reevaluate decision to keep styleguide promoting different
indentation for python and shell tasks? Otherwise we should mention
different rules for oe-core and other layers.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-04-24 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 21:47 OpenEmbedded TSC 8 April 2013 Jeff Osier-Mixon
2013-04-24 6:43 ` Martin Jansa [this message]
2013-04-24 8:01 ` [oe] " Richard Purdie
2013-04-24 8:22 ` Martin Jansa
2013-04-24 10:39 ` Phil Blundell
2013-04-24 12:31 ` 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=20130424064319.GD3217@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox