From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] go: Add recipes for golang compilers and tools
Date: Mon, 14 Nov 2016 15:00:34 +0200 [thread overview]
Message-ID: <dce6aa96-0ebb-6158-e9fa-f5074ec1fadd@linux.intel.com> (raw)
In-Reply-To: <1478887474.23123.233.camel@linuxfoundation.org>
On 11/11/2016 08:04 PM, Richard Purdie wrote:
> This was something that came up at OEDEM. There are several layers with
> several attempts at getting this right, most have some issues.
>
> Whilst we've been pulling things out of core, we also need to consider
> things that perhaps should get added. Having this in core would
> certainly address a number of issues (but is also potentially a
> maintenance burden).
>
> We did agree there that we'd consider this. Obviously input from people
> not there is welcome though and this does need discussion. I'm leaning
> moderately in favour of adding it as things stand.
I guess I would be more open to this if Khem at the same time sent a
patch that explicitly assigns maintainership of all those new recipes.
So please don't merge until that is agreed and done.
Alex
next prev parent reply other threads:[~2016-11-14 13:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 0:39 [PATCH 1/2] go: Add recipes for golang compilers and tools Khem Raj
2016-11-10 0:39 ` [PATCH 2/2] go-examples: Add an example, helloworld written in go Khem Raj
2016-11-11 2:59 ` Christopher Larson
2016-11-14 2:07 ` Khem Raj
2016-11-11 13:10 ` [PATCH 1/2] go: Add recipes for golang compilers and tools Alexander Kanavin
2016-11-11 16:02 ` Khem Raj
2016-11-11 16:44 ` Bruce Ashfield
2016-11-11 16:52 ` Burton, Ross
2016-11-11 18:04 ` Richard Purdie
2016-11-14 13:00 ` Alexander Kanavin [this message]
2016-11-14 17:49 ` Khem Raj
2016-11-15 18:43 ` Matt Madison
2016-11-11 17:16 ` Maciej Borzęcki
2016-11-11 18:11 ` Khem Raj
2016-12-12 12:36 ` Gary Thomas
2016-12-12 18:02 ` Khem Raj
2017-01-25 19:40 ` Maciej Borzęcki
2017-01-25 19:57 ` Khem Raj
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=dce6aa96-0ebb-6158-e9fa-f5074ec1fadd@linux.intel.com \
--to=alexander.kanavin@linux.intel.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