From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libkrb5: Bumb to 1.17
Date: Mon, 30 Sep 2019 22:18:15 +0200 [thread overview]
Message-ID: <20190930221815.6d06ffcb@windsurf.home> (raw)
In-Reply-To: <20190930113931.9654-1-nerv@dawncrow.de>
Hello,
On Mon, 30 Sep 2019 13:39:31 +0200
Andr? Hentschel <nerv@dawncrow.de> wrote:
> Signed-off-by: Andr? Hentschel <nerv@dawncrow.de>
Typo in the commit title: Bumb -> Bump. Also, you should have explained
in the commit log why the hash of the NOTICE file has changed, and what
are the changes. Indeed, this is important to check what license
changes happened. In this case, nothing was really relevant. I've
applied after extending the commit log.
However, I think this package license information may not be totally
correct, independently of this version bump. Indeed, our libkrb5.mk
says the license is MIT, but the NOTICE file shows a bunch of parts
under BSD-2-Clause for example.
Arnout, Yann, what do you think about this? It's one of those packages
with lots of code re-used from different projects, all under
MIT/BSD-2-Clause style licenses. I'd be interested to hear your opinion
on the matter.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-30 20:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 11:39 [Buildroot] [PATCH] package/libkrb5: Bumb to 1.17 André Hentschel
2019-09-30 20:18 ` Thomas Petazzoni [this message]
2019-09-30 20:28 ` Yann E. MORIN
2019-09-30 22:13 ` Arnout Vandecappelle
2019-10-01 15:33 ` Yann E. MORIN
2019-10-01 15:41 ` Arnout Vandecappelle
2019-10-01 15:44 ` Thomas Petazzoni
2019-10-01 17:45 ` Yann E. MORIN
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=20190930221815.6d06ffcb@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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