Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] recipes: Move out stale GPLv2 versions to a seperate layer
Date: Wed, 08 Mar 2017 11:23:15 +0000	[thread overview]
Message-ID: <1488972195.2982.5.camel@linux.intel.com> (raw)
In-Reply-To: <1488971483.22968.64.camel@linuxfoundation.org>

On Wed, 2017-03-08 at 11:11 +0000, Richard Purdie wrote:
> On Wed, 2017-03-08 at 09:34 +0000, Peter Kjellerstedt wrote:
> > 
> > And the layer should be added to the layer index...
> 
> Yes, it should.

I've submitted meta-gplv2 to the layer index.

Joshua


      reply	other threads:[~2017-03-08 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 18:22 [PATCH] recipes: Move out stale GPLv2 versions to a seperate layer Richard Purdie
2017-03-07 18:31 ` Andre McCurdy
2017-03-08  9:34 ` Peter Kjellerstedt
2017-03-08 11:11   ` Richard Purdie
2017-03-08 11:23     ` Joshua Lock [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=1488972195.2982.5.camel@linux.intel.com \
    --to=joshua.g.lock@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    --cc=richard.purdie@linuxfoundation.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