Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] common-licenses: Adding bzip
Date: Fri, 05 Oct 2012 09:04:24 -0700	[thread overview]
Message-ID: <506F0508.30404@linux.intel.com> (raw)
In-Reply-To: <CAPhnLPCTDCOhz2Na9ehrWUbD0XQGos5HWbXyVS-LCVKLR2Ev9w@mail.gmail.com>

On 10/03/2012 12:41 PM, Flanagan, Elizabeth wrote:
> bzip requires it's own specific license.
>
> Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
> ---
>   meta/files/common-licenses/bzip |   41 +++++++++++++++++++++++++++++++++++++++
>   1 file changed, 41 insertions(+)
>   create mode 100644 meta/files/common-licenses/bzip
>

Merged into OE-Core

Thanks
	Sau!


> diff --git a/meta/files/common-licenses/bzip b/meta/files/common-licenses/bzip
> new file mode 100644
> index 0000000..2162888
> --- /dev/null
> +++ b/meta/files/common-licenses/bzip
> @@ -0,0 +1,41 @@
> +--------------------------------------------------------------------------
> +
> +This program, "bzip2", the associated library "libbzip2", and all
> +documentation, are copyright (C) 1996-2010 Julian R Seward.  All
> +rights reserved.
> +
> +Redistribution and use in source and binary forms, with or without
> +modification, are permitted provided that the following conditions
> +are met:
> +
> +1. Redistributions of source code must retain the above copyright
> +   notice, this list of conditions and the following disclaimer.
> +
> +2. The origin of this software must not be misrepresented; you must
> +   not claim that you wrote the original software.  If you use this
> +   software in a product, an acknowledgment in the product
> +   documentation would be appreciated but is not required.
> +
> +3. Altered source versions must be plainly marked as such, and must
> +   not be misrepresented as being the original software.
> +
> +4. The name of the author may not be used to endorse or promote
> +   products derived from this software without specific prior written
> +   permission.
> +
> +THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS
> +OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> +WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
> +ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
> +DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
> +DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
> +GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
> +INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
> +WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
> +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> +
> +Julian Seward, jseward@bzip.org
> +bzip2/libbzip2 version 1.0.6 of 6 September 2010
> +
> +--------------------------------------------------------------------------
>



      reply	other threads:[~2012-10-05 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 19:41 [PATCH 1/1] common-licenses: Adding bzip Flanagan, Elizabeth
2012-10-05 16:04 ` 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=506F0508.30404@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=elizabeth.flanagan@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox