From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Buildroot support for Intel X1000
Date: Tue, 20 Oct 2015 11:36:22 +0200 [thread overview]
Message-ID: <20151020113622.6c4e1625@free-electrons.com> (raw)
In-Reply-To: <1445333306.3204.6.camel@intel.com>
Dear Kinsella, Ray,
On Tue, 20 Oct 2015 09:28:27 +0000, Kinsella, Ray wrote:
> I took a quick check of my board/galileo patchset.
> It is free for errant trailing spaces and has the required "category"
> prefix.
Thanks for checking.
> However, I had a question on tabbing, for files like grub.cfg or
> genimage.cfg.
> Is there a convention? are tabs _or_ spaces fine?
I think we more commonly use tabs.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-10-20 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 11:02 [Buildroot] [PATCH] Buildroot support for Intel X1000 Kinsella, Ray
2015-10-19 21:48 ` Arnout Vandecappelle
2015-10-20 8:06 ` Thomas Petazzoni
2015-10-20 9:28 ` Kinsella, Ray
2015-10-20 9:36 ` Thomas Petazzoni [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=20151020113622.6c4e1625@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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