From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V2] dejavu: Add missing license name and license hash
Date: Wed, 24 Jul 2019 00:25:14 +0200 [thread overview]
Message-ID: <20190724002514.2e252e64@windsurf> (raw)
In-Reply-To: <20190723152816.20465-1-mickael.tansorier@smile.fr>
Hello,
Adding Yann and Arnout (licensing question below)
On Tue, 23 Jul 2019 17:28:16 +0200
Micka?l Tansorier <mickael.tansorier@smile.fr> wrote:
> There is 3 licenses, not listed in SPDX license list:
> - Bitstream Vera Fonts
> - Arev Fonts
> - Public Domain
I'm not sure what you mean in this commit log. The actual code change
is to add "Bitstream Vera" to the list of licenses, which is also not
part of the SPDX license list.
Regarding SPDX and "Public Domain", see
https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_Files.
Also, I think you are misreading the LICENSE file. What it says is
"Bitstream Vera Fonts Copyright" and "Arev Fonts Copyright", which are
not license texts. The license text is below each of those titles.
Here is what Debian says about this font:
https://metadata.ftp-master.debian.org/changelogs//main/f/fonts-dejavu/fonts-dejavu_2.37-1_copyright
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-07-23 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 15:28 [Buildroot] [PATCH V2] dejavu: Add missing license name and license hash Mickaël Tansorier
2019-07-23 22:25 ` Thomas Petazzoni [this message]
2019-08-26 9:34 ` Mickaël Tansorier
2019-10-24 12:08 ` Mickaël Tansorier
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=20190724002514.2e252e64@windsurf \
--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