Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 6/6] libxsettings-client: fix LICENSE
Date: Tue, 26 Apr 2016 08:44:41 +0800	[thread overview]
Message-ID: <571EB9F9.3060602@windriver.com> (raw)
In-Reply-To: <CAJTo0LZgtTN+6M_Xvwm2zQAibJR0jBXB15eU12HfUtz2ERuYKA@mail.gmail.com>



On 04/25/2016 11:26 PM, Burton, Ross wrote:
>
> On 25 April 2016 at 14:51, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
>
>     The tarball has a COPYING file now, and is GPLv2+.
>
>
> Just had a proper look at this.  The tarball has a COPYING that says GPL, but
> the source files are all clearly marked MIT.

Thanks, did you mean the following text ? I can't find MIT license there.

/*
  * Copyright © 2001 Red Hat, Inc
  *
  * Permission to use, copy, modify, distribute, and sell this software and its
  * documentation for any purpose is hereby granted without fee, provided that
  * the above copyright notice appear in all copies and that both that
  * copyright notice and this permission notice appear in supporting
  * documentation, and that the name of Red Hat not be used in advertising or
  * publicity pertaining to distribution of the software without specific,
  * written prior permission.  Red Hat makes no representations about the
  * suitability of this software for any purpose.  It is provided "as is"
  * without express or implied warranty.
  *
  * RED HAT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
  * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL RED HAT
  * BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
  * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
  * OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
  * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
  *
  * Author:  Owen Taylor, Red Hat, Inc.
  */

// Robert

>
> Ross


  reply	other threads:[~2016-04-26  0:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 13:51 [PATCH 0/6] insane.bbclass: package_qa_check_license -> do_qa_populate_lic Robert Yang
2016-04-25 13:51 ` [PATCH 1/6] insane.bbclass: remove workdir from package_qa_check_license() Robert Yang
2016-04-25 13:51 ` [PATCH 2/6] insane.bbclass: package_qa_check_license -> do_qa_populate_lic Robert Yang
2016-04-26  8:56   ` Richard Purdie
2016-04-26  9:01     ` Robert Yang
2016-04-27  2:28     ` Robert Yang
2016-04-25 13:51 ` [PATCH 3/6] packagegroup.bbclass: set LICENSE and LIC_FILES_CHKSUM Robert Yang
2016-04-25 13:51 ` [PATCH 4/6] packagegroup-foo.bb: remove LICENSE = "MIT" Robert Yang
2016-04-25 13:51 ` [PATCH 5/6] meta-world-pkgdata: add LIC_FILES_CHKSUM Robert Yang
2016-04-25 13:51 ` [PATCH 6/6] libxsettings-client: fix LICENSE Robert Yang
2016-04-25 15:26   ` Burton, Ross
2016-04-26  0:44     ` Robert Yang [this message]
2016-04-26 13:29       ` Burton, Ross
2016-04-26 13:57         ` Flanagan, Elizabeth
2016-04-26 16:43           ` Khem Raj
2016-04-26 16:56             ` Burton, Ross
2016-04-27  1:18               ` Robert Yang

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=571EB9F9.3060602@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox