From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] neon: add the recipe from oe-core
Date: Thu, 23 Nov 2017 15:39:39 +0200 [thread overview]
Message-ID: <5f24aa16-b33b-6e44-c23c-aefbbc8c7117@linux.intel.com> (raw)
In-Reply-To: <CA+chaQf6LKVf5vRBSAmUxue2wb253o2bHs5XjN2CoL2t0Ox4MQ@mail.gmail.com>
On 11/23/2017 02:06 PM, Martin Jansa wrote:
> https://www.openembedded.org/wiki/Styleguide#Format_Guidelines
Alright. I resent the patch, as I don't want to start a style war, but
(as discussed previously) I will resist any attempts to enforce
indentation in oe-core. We need to prioritize what we spend our time on
ruthlessly, considering the project is constantly under-staffed.
Alex
next prev parent reply other threads:[~2017-11-23 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 16:30 [PATCH] neon: add the recipe from oe-core Alexander Kanavin
2017-11-22 17:47 ` Martin Jansa
2017-11-23 9:46 ` Alexander Kanavin
2017-11-23 12:06 ` Martin Jansa
2017-11-23 13:39 ` Alexander Kanavin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-23 13:36 Alexander Kanavin
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=5f24aa16-b33b-6e44-c23c-aefbbc8c7117@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@gmail.com \
--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.