From: Adrian Bunk <bunk@stusta.de>
To: Chen Qi <Qi.Chen@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] util-linux: upgrade to 2.33.2
Date: Wed, 12 Jun 2019 08:43:05 +0300 [thread overview]
Message-ID: <20190612054305.GB12642@localhost> (raw)
In-Reply-To: <6c141cf1421c58dd5fed46481b94c82143628bab.1560305170.git.Qi.Chen@windriver.com>
On Wed, Jun 12, 2019 at 10:06:33AM +0800, Chen Qi wrote:
> The license files' names are changed, but the contents remain the
> same.
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> meta/recipes-core/util-linux/util-linux.inc | 16 ++++++++--------
> .../{util-linux_2.32.1.bb => util-linux_2.33.2.bb} | 4 ++--
> 2 files changed, 10 insertions(+), 10 deletions(-)
> rename meta/recipes-core/util-linux/{util-linux_2.32.1.bb => util-linux_2.33.2.bb} (72%)
>
> diff --git a/meta/recipes-core/util-linux/util-linux.inc b/meta/recipes-core/util-linux/util-linux.inc
> index 7b9b4d2..eaaf408 100644
> --- a/meta/recipes-core/util-linux/util-linux.inc
> +++ b/meta/recipes-core/util-linux/util-linux.inc
> @@ -8,15 +8,15 @@ SECTION = "base"
>
> LICENSE = "GPLv2+ & LGPLv2.1+ & BSD"
>...
> - file://Documentation/licenses/COPYING.UCB;md5=263860f8968d8bafa5392cab74285262 \
>...
> + file://Documentation/licenses/COPYING.BSD-4-Clause-UC;md5=263860f8968d8bafa5392cab74285262 \
>...
Doesn't this mean that LICENSE is (and already was before) wrong?
meta/files/common-licenses/BSD is the 3 clause BSD licence,
but this is the 4 clause licence (with the advertising clause).
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-06-12 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 2:06 [PATCH 0/1] util-linux: upgrade to 2.33.2 Chen Qi
2019-06-12 2:06 ` [PATCH 1/1] " Chen Qi
2019-06-12 5:43 ` Adrian Bunk [this message]
2019-06-12 6:08 ` ChenQi
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=20190612054305.GB12642@localhost \
--to=bunk@stusta.de \
--cc=Qi.Chen@windriver.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.