From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] at: add license information
Date: Fri, 04 Jul 2014 16:13:01 +0200 [thread overview]
Message-ID: <87lhs95i1e.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1404417639-5879-1-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Thu, 3 Jul 2014 17:00:36 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/at/at.mk | 2 ++
> 1 file changed, 2 insertions(+)
> diff --git a/package/at/at.mk b/package/at/at.mk
> index 0fe5b9a..f09548d 100644
> --- a/package/at/at.mk
> +++ b/package/at/at.mk
> @@ -11,6 +11,8 @@ AT_SITE = $(BR2_DEBIAN_MIRROR)/debian/pool/main/a/at
> AT_MAKE = $(MAKE1)
> AT_AUTORECONF = YES
> AT_DEPENDENCIES = $(if $(BR2_PACKAGE_FLEX),flex) host-bison host-flex
> +AT_LICENSE = GPLv2+
> +AT_LICENSE_FILES = Copyright
That file lists files under GPLv2+, GPLv3+ and the NTP
license. parsetime.pl is only used for 'make test', but wouldn't the
combined license be GPLv3+ instead?
The COPYING file (which we probably should add to _LICENSE_FILES) is
GPLv2 though.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-07-04 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 20:00 [Buildroot] [PATCH 1/4] at: add license information Gustavo Zacarias
2014-07-03 20:00 ` [Buildroot] [PATCH 2/4] bootutils: " Gustavo Zacarias
2014-07-09 13:34 ` Peter Korsgaard
2014-07-03 20:00 ` [Buildroot] [PATCH 3/4] cloop: " Gustavo Zacarias
2014-07-09 13:42 ` Peter Korsgaard
2014-07-03 20:00 ` [Buildroot] [PATCH 4/4] cryptodev-linux: fix " Gustavo Zacarias
2014-07-09 13:45 ` Peter Korsgaard
2014-07-04 14:13 ` Peter Korsgaard [this message]
2014-07-04 14:17 ` [Buildroot] [PATCH 1/4] at: add " Gustavo Zacarias
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=87lhs95i1e.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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