From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3,1/2] brltty: add license
Date: Tue, 18 Sep 2018 22:50:55 +0200 [thread overview]
Message-ID: <20180918225055.391107cd@windsurf> (raw)
In-Reply-To: <20180916145511.7304-1-fontaine.fabrice@gmail.com>
Hello,
On Sun, 16 Sep 2018 16:55:10 +0200, Fabrice Fontaine wrote:
> brltty 5.5 is licensed under GPL-2.0+ with exceptions in LGPL-2.1+ for
> data and client side as specified in README so add this information in
> BRLTTY_LICENSE, update BRLTTY_LICENSE_FILES and add hash for README
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v2 -> v3 (after review of Thomas Petazzoni):
> - Be more precise in BRLTTY_LICENSE
Both applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-18 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 14:55 [Buildroot] [PATCH v3,1/2] brltty: add license Fabrice Fontaine
2018-09-16 14:55 ` [Buildroot] [PATCH v3,2/2] brltty: bump to version 5.6 Fabrice Fontaine
2018-09-18 20:50 ` Thomas Petazzoni [this message]
2018-10-05 11:34 ` [Buildroot] [PATCH v3,1/2] brltty: add license Peter Korsgaard
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=20180918225055.391107cd@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