From: Paul Barker <paul@paulbarker.me.uk>
To: Openembedded Discussion <openembedded-devel@lists.openembedded.org>
Cc: Yu Zongchun-B40527 <B40527@freescale.com>
Subject: Re: [meta-oe][PATCH] iperf: Fix license
Date: Tue, 30 Jul 2013 15:14:51 +0100 [thread overview]
Message-ID: <CANyK_8cA_iJLsfq5R1dgtS6L95zyDz5iNNTcWOYP1LnN36+DZQ@mail.gmail.com> (raw)
In-Reply-To: <B21730BB6DA1D24B83348D9301EA417E1042EA39@039-SN2MPN1-023.039d.mgd.msft.net>
On 29 July 2013 10:45, Guo Chunrong-B40290 <B40290@freescale.com> wrote:
> Hello,
>
> I'd appreciate if someone can review.
>
I'll take a quick look...
> -LICENSE = "NewBSD"
> +LICENSE = "BSD"
Comparing http://sourceforge.net/p/iperf/code/82/tree/trunk/COPYING
and the common licenses in openembedded-core, it looks like
"BSD-2-Clause" would be more accurate. Could you take a look and let
me know if you agree? Currently on the move so can't diff the files
myself.
--
Paul Barker
Email: paul@paulbarker.me.uk
http://www.paulbarker.me.uk
next prev parent reply other threads:[~2013-07-30 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 9:27 [meta-oe][PATCH] iperf: Fix license Chunrong Guo
2013-07-29 9:45 ` Guo Chunrong-B40290
2013-07-30 14:14 ` Paul Barker [this message]
2013-07-31 2:04 ` Guo Chunrong-B40290
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=CANyK_8cA_iJLsfq5R1dgtS6L95zyDz5iNNTcWOYP1LnN36+DZQ@mail.gmail.com \
--to=paul@paulbarker.me.uk \
--cc=B40527@freescale.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.