From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] docs: Added referenc to EUPL
Date: Wed, 28 May 2014 18:02:44 +0200 [thread overview]
Message-ID: <538608A4.8050104@mind.be> (raw)
In-Reply-To: <1401005324-10428-1-git-send-email-oli.vogt.pub01@gmail.com>
Hi Olli,
It would make more sense to submit this patch as part of a series adding a
package that actually uses the license.
Also:
On 25/05/14 10:08, oli vogt wrote:
> The first European Union Public Licence
>
> Signed-off-by: oli vogt <oli.vogt.pub01@gmail.com>
> ---
> docs/manual/legal-notice.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
> index d4344b9..42a4a52 100644
> --- a/docs/manual/legal-notice.txt
> +++ b/docs/manual/legal-notice.txt
> @@ -122,6 +122,9 @@ Buildroot, with the name used in the manifest files:
> * `Apache-2.0`:
> http://apache.org/licenses/LICENSE-2.0.html[
> Apache License, version 2.0];
> +* `EUPL-1`:
spdx.org has EUPL-1.0 and EUPL-1.1. I expect only EUPL-1.1 is relevant.
> + http://ec.europa.eu/idabc/eupl.html[
> + The first European Union Public Licence];
"The first"? The website refers to it as v1.1. So I'd call it
European Union Public License, version 1.1
Regards,
Arnout
>
> == Complying with the Buildroot license
>
>
--
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:[~2014-05-28 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 8:08 [Buildroot] [PATCH 2/2] docs: Added referenc to EUPL oli vogt
2014-05-25 19:54 ` Peter Korsgaard
2014-05-25 23:04 ` oli vogt
2014-05-28 16:02 ` Arnout Vandecappelle [this message]
2014-06-11 20:08 ` Thomas Petazzoni
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=538608A4.8050104@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