From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>, Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] go: Add recipes for golang compilers and tools
Date: Wed, 08 Feb 2017 13:53:03 +0000 [thread overview]
Message-ID: <1486561983.3754.4.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LaapTyVGhiB9AfnWznNU1z8-dbJC=7+JOThYHb2HEM2=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
On Tue, 2017-02-07 at 17:35 +0000, Burton, Ross wrote:
> On 7 February 2017 at 04:24, Khem Raj <raj.khem@gmail.com> wrote:
> > This is converging the recipes for go from
> >
> > meta-virtualization and oe-meta-go
> >
>
> I'm still of the opinion that this should be in meta-go, not oe-
> core...
FWIW I disagree. Go is a popular systems language and we're
increasingly supporting a wide-array of systems with OE (from iot to
ivi and beyond).
Go is already in wide enough use and duplicated in enough layers that
we would be doing folks a favour by including it in OE-Core and our
build/test cycle.
Joshua
[-- Attachment #2: Type: text/html, Size: 1035 bytes --]
next prev parent reply other threads:[~2017-02-08 13:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 4:24 [PATCH 1/3] go: Add recipes for golang compilers and tools Khem Raj
2017-02-07 4:24 ` [PATCH 2/3] go-examples: Add an example, helloworld written in go Khem Raj
2017-02-07 4:24 ` [PATCH 3/3] go: Fix go cross build with rss Khem Raj
2017-02-07 17:35 ` [PATCH 1/3] go: Add recipes for golang compilers and tools Burton, Ross
2017-02-07 17:44 ` Khem Raj
2017-02-07 20:17 ` Paul Eggleton
2017-02-07 20:42 ` Mark Asselstine
2017-02-08 12:46 ` Matt Madison
2017-02-08 13:53 ` Joshua Lock [this message]
2017-02-08 13:57 ` Gary Thomas
2017-02-08 14:07 ` Jussi Kukkonen
2017-02-08 14:18 ` Burton, Ross
2017-02-08 14:16 ` Alexander Kanavin
2017-02-08 13:57 ` Bruce Ashfield
2017-02-08 14:00 ` Richard Purdie
2017-02-12 7:36 ` Khem Raj
2017-02-12 14:20 ` Maciej Borzęcki
2017-02-12 14:51 ` Maciej Borzęcki
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=1486561983.3754.4.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross.burton@intel.com \
/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.