From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "Roland Hieber" <rhi@pengutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] commands/*: Replace license boilerplate by SPDX identfiers
Date: Tue, 21 Apr 2020 10:15:09 +0200 [thread overview]
Message-ID: <ee2da995-8431-cedc-5be9-ea728892bbbd@pengutronix.de> (raw)
In-Reply-To: <20200420084657.7vqzmu5g5aj63sza@pengutronix.de>
Hi,
On 4/20/20 10:46 AM, Roland Hieber wrote:
> On Fri, Apr 17, 2020 at 10:33:08PM +0200, Uwe Kleine-König wrote:
>> While at it also drop references to the non-existing CREDITS file.
>>
>> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>> ---
>> Hello,
>>
>> there is one file (2048.c) that specifies the MIT license. I wonder if
>> we should use "GPL-2.0 OR MIT" there as effectively as distributed with
>> barebox it is licensed under the GPL 2, isn't it?
>
> I would stay as close to the source as possible. MIT and GPL-2.0 are
> compatible, so there is no problem on the project level, and I see no
> reason to handle this on the level of individual files.
We need a copy of the MIT license in LICENSES/ though, before we reference
it. Thinking about it, we already reference MIT (and X11) in the dts/
directory. So both should be added.
Cheers,
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-04-21 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 20:33 Uwe Kleine-König
2020-04-20 8:46 ` Roland Hieber
2020-04-21 8:15 ` Ahmad Fatoum [this message]
2020-04-21 21:08 ` Uwe Kleine-König
2020-04-20 12:55 ` Roland Hieber
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=ee2da995-8431-cedc-5be9-ea728892bbbd@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rhi@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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