From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Jeff Lance <j-lance1@ti.com>
Subject: Re: [PATCH 1/1 v2] trace-cmd: modifying License information
Date: Tue, 13 Mar 2012 09:20:27 -0700 [thread overview]
Message-ID: <4F5F73CB.7040602@linux.intel.com> (raw)
In-Reply-To: <1331060029-6748-1-git-send-email-j-lance1@ti.com>
On 03/06/2012 10:53 AM, Jeff Lance wrote:
> * Adding "GPLv2& LGPLv2.1" to create a dual license to cover the libraries.
> * Bump up PR
>
> Signed-off-by: Jeff Lance<j-lance1@ti.com>
> ---
> Updated in version 2:
> Added '&' to indicate both licenses apply
> ---
> meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb | 8 +++++---
> 1 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb b/meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb
> index d40dc6e..7f6f6cf 100644
> --- a/meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb
> +++ b/meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb
> @@ -1,10 +1,12 @@
> DESCRIPTION = "User interface to Ftrace"
> -LICENSE = "GPLv2"
> +LICENSE = "GPLv2& LGPLv2.1"
> LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
> - file://trace-cmd.c;beginline=6;endline=8;md5=2c22c965a649ddd7973d7913c5634a5e"
> + file://trace-cmd.c;beginline=6;endline=8;md5=2c22c965a649ddd7973d7913c5634a5e \
> + file://COPYING.LIB;md5=bbb461211a33b134d42ed5ee802b37ff \
> + file://trace-input.c;beginline=5;endine=8;md5=c9c405aaf5cfc09582ec83cf6e83a020"
>
> SRCREV = "7055ffd37beeb44714e86a4abc703f7e175a0db5"
> -PR = "r1"
> +PR = "r2"
> PV = "1.2+git${SRCPV}"
>
> inherit pkgconfig
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-03-13 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 18:53 [PATCH 1/1 v2] trace-cmd: modifying License information Jeff Lance
2012-03-13 16:20 ` Saul Wold [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=4F5F73CB.7040602@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=j-lance1@ti.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 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.