From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] boot/at91bootstrap3: add license information
Date: Mon, 01 Jun 2015 21:17:42 +0200 [thread overview]
Message-ID: <556CAFD6.3060306@mind.be> (raw)
In-Reply-To: <CA+TH9VnxnMj6SXxAagocarZWtay9kXvQhqPVTvQs26Jn=UNxgA@mail.gmail.com>
On 06/01/15 18:03, Angelo Compagnucci wrote:
> Dear Thomas Petazzoni,
>
> 2015-05-31 10:43 GMT+02:00 Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com>:
>> Dear Angelo Compagnucci,
>>
>> On Fri, 29 May 2015 11:38:44 +0200, Angelo Compagnucci wrote:
>>> This patch adds licensing informations to at91bootstrap3
>>>
>>> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
>>> ---
>>> boot/at91bootstrap3/at91bootstrap3.mk | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/boot/at91bootstrap3/at91bootstrap3.mk b/boot/at91bootstrap3/at91bootstrap3.mk
>>> index ff49e14..2164a74 100644
>>> --- a/boot/at91bootstrap3/at91bootstrap3.mk
>>> +++ b/boot/at91bootstrap3/at91bootstrap3.mk
>>> @@ -6,6 +6,8 @@
>>>
>>> AT91BOOTSTRAP3_VERSION = v3.7.1
>>> AT91BOOTSTRAP3_SITE = $(call github,linux4sam,at91bootstrap,$(AT91BOOTSTRAP3_VERSION))
>>> +AT91BOOTSTRAP3_LICENSE = BSD-2c
>>> +AT91BOOTSTRAP3_LICENSE_FILES = main.c
>>
>> I *think* it is actually closer to a BSD-3c, since it has the following
>> text:
>>
>> * Atmel's name may not be used to endorse or promote products derived from
>> * this software without specific prior written permission.
>>
>> However, the wording is not 100% the one of the BSD-3c, so I'm not sure
>> if we should call it BSD-3c or not.
>
> Probably you are right, the wording is more similar to a BSD-3c
> instead of a BSD-2c, but it's different. Can we use something like
> BSD-custom or BSD-modified?
I would say
BSD-2c with endorsement clause
That's still relatively short but also clear.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-06-01 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 9:38 [Buildroot] [PATCH 0/3] Caring at91bootstrap3 Angelo Compagnucci
2015-05-29 9:38 ` [Buildroot] [PATCH 1/3] boot/at91bootstrap3: add license information Angelo Compagnucci
2015-05-31 8:43 ` Thomas Petazzoni
2015-06-01 16:03 ` Angelo Compagnucci
2015-06-01 19:17 ` Arnout Vandecappelle [this message]
2015-05-29 9:38 ` [Buildroot] [PATCH 2/3] boot/at91bootstrap3: bump to version 3.7.2 Angelo Compagnucci
2015-05-29 9:38 ` [Buildroot] [PATCH 3/3] boot/at91bootstrap3: download via custom git url Angelo Compagnucci
2015-06-01 19:35 ` Arnout Vandecappelle
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=556CAFD6.3060306@mind.be \
--to=arnout@mind.be \
--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