From: Michael Wood <michael.g.wood@intel.com>
To: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: [RFC] Coding style guide
Date: Wed, 01 Apr 2015 16:06:17 +0100 [thread overview]
Message-ID: <551C0969.2070301@intel.com> (raw)
I think it would be good if we adopted an agreed on code style guide so
that we can gain some consistency in the code for readability in new
contributions.
Note that I don't want to become one of those projects that bike-sheds
every patch on the code style! Which is why I'm calling them
guides/recommendations.
I've written up some here:
https://wiki.yoctoproject.org/wiki/Contribute_to_Toaster#Style_guide_DRAFT
http://tinyurl.com/ocykv2s
It's by no means complete but would like to get some comments first.
Michael
reply other threads:[~2015-04-01 15:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=551C0969.2070301@intel.com \
--to=michael.g.wood@intel.com \
--cc=toaster@yoctoproject.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.