From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] at: add license information
Date: Fri, 04 Jul 2014 11:17:37 -0300 [thread overview]
Message-ID: <53B6B781.3050909@zacarias.com.ar> (raw)
In-Reply-To: <87lhs95i1e.fsf@dell.be.48ers.dk>
On 07/04/2014 11:13 AM, Peter Korsgaard wrote:
> > +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.
Yeah i went for Copyright because of the complexities.
at.c which we could call main() is GPLv2+
parsetime.pl should be ingnored (tests, not installed, not used).
Only posixtm.c is v3+ but since it's linked to the other bits that are
v2+ the whole thing should probably be called v3+ (you can go down is my
interpretation, but you can go up).
Regards.
prev parent reply other threads:[~2014-07-04 14:17 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 ` [Buildroot] [PATCH 1/4] at: add " Peter Korsgaard
2014-07-04 14:17 ` Gustavo Zacarias [this message]
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=53B6B781.3050909@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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