From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] libcgicc: bump to version 3.2.13
Date: Sun, 30 Mar 2014 11:30:51 +0200 [thread overview]
Message-ID: <20140330113051.5c43cc69@skate> (raw)
In-Reply-To: <1396135140-1402-2-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Sat, 29 Mar 2014 20:19:00 -0300, Gustavo Zacarias wrote:
> Also add license files and docs license definition.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/libcgicc/libcgicc.mk | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Applied, thanks, with one minor change.
> +LIBCGICC_LICENSE = LGPLv3+, docs: GFDL1.2+
I've changed this to the more traditional:
LGPLv3+ (library), GFDL1.2+ (docs)
Though I'm wondering if:
* We shouldn't use GFDLv1.2+ instead, like we do for GPL/LGPL.
* Whether we should really worry about the documentation license,
since we don't allow the installation of the documentation on the
target. I don't think we have any other package that describe the
license of their documentation.
Cc'ing Luca and Yann to get an opinion on this.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-30 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 23:18 [Buildroot] [PATCH 1/2] radvd: bump to version 1.10.0 Gustavo Zacarias
2014-03-29 23:19 ` [Buildroot] [PATCH 2/2] libcgicc: bump to version 3.2.13 Gustavo Zacarias
2014-03-30 9:30 ` Thomas Petazzoni [this message]
2014-03-30 10:22 ` Gustavo Zacarias
2014-03-30 10:27 ` Thomas Petazzoni
2014-03-30 10:32 ` Yann E. MORIN
2014-03-30 13:55 ` Luca Ceresoli
2014-03-30 9:28 ` [Buildroot] [PATCH 1/2] radvd: bump to version 1.10.0 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=20140330113051.5c43cc69@skate \
--to=thomas.petazzoni@free-electrons.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