Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 06/18] cmake: update to 3.7.0
Date: Tue, 29 Nov 2016 16:01:07 +0200	[thread overview]
Message-ID: <0fb9060b-1019-fb87-3559-ffe8eb46efc7@linux.intel.com> (raw)
In-Reply-To: <57D1D0A9-6C79-4556-A863-A6553364746E@gmail.com>

On 11/29/2016 01:24 AM, Khem Raj wrote:
>
>> On Nov 28, 2016, at 5:34 AM, Alexander Kanavin <alexander.kanavin@linux.intel.com> wrote:
>>
>> License is still 3-clause BSD.
>
> OK. what triggered the checksum change then ?

They added a contributor list to Copyright.txt (I'll trim the lines that 
are checksummed if that list will be constantly changing), and changed 
the header in cmake.h from

/*============================================================================
   CMake - Cross Platform Makefile Generator
   Copyright 2000-2009 Kitware, Inc., Insight Software Consortium

   Distributed under the OSI-approved BSD License (the "License");
   see accompanying file Copyright.txt for details.

   This software is distributed WITHOUT ANY WARRANTY; without even the
   implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
   See the License for more information.
============================================================================*/

to

/* Distributed under the OSI-approved BSD 3-Clause License.  See 
accompanying
    file Copyright.txt or https://cmake.org/licensing for details.  */

Alex



  reply	other threads:[~2016-11-29 14:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 13:34 [PATCH 00/18] Recipe version updates Alexander Kanavin
2016-11-28 13:34 ` [PATCH 01/18] icu: update to 58.1 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 02/18] sysprof: update to 3.22.2 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 03/18] btrfs-tools: update to 4.8.4 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 04/18] ca-certificates: upgrade to 20161102 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 05/18] lighttpd: upgrade to 1.4.43 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 06/18] cmake: update to 3.7.0 Alexander Kanavin
2016-11-28 23:24   ` Khem Raj
2016-11-29 14:01     ` Alexander Kanavin [this message]
2016-11-29 17:20       ` Khem Raj
2016-11-28 13:34 ` [PATCH 07/18] gnome-desktop3: update to 3.22.2 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 08/18] upstream-version-is-even.bbclass: ensure that the full version is matched Alexander Kanavin
2016-11-28 13:34 ` [PATCH 09/18] gnutls: update to 3.5.6 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 10/18] gobject-introspection: update to 1.50.0 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 11/18] iso-codes: update to 3.71 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 12/18] msmtp: update to 1.6.6 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 13/18] npth: update to 1.3 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 14/18] vala: update to 0.34.3 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 15/18] rng-tools: use SOURCEFORGE_MIRROR in SRC_URI Alexander Kanavin
2016-11-28 13:34 ` [PATCH 16/18] webkitgtk: update to 2.14.2 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 17/18] epiphany: update to 3.22.3 Alexander Kanavin
2016-11-28 13:34 ` [PATCH 18/18] ffmpeg: update to 3.2.1 Alexander Kanavin

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=0fb9060b-1019-fb87-3559-ffe8eb46efc7@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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