From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 02/10] dialog: add license information
Date: Mon, 04 Feb 2013 20:30:55 -0300 [thread overview]
Message-ID: <511044AF.8080700@zacarias.com.ar> (raw)
In-Reply-To: <87obfzy91n.fsf@dell.be.48ers.dk>
On 02/04/2013 08:05 PM, Peter Korsgaard wrote:
> Ahh, you're right. So we have 33 .c files (including the main one) not
> listing 'or later', and a single one which does.
>
> What does that mean?
Unfortunately it seems to be quite a debate, see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632198
Problem is that one file says "or later" and the rest doesn't.
I'm not a lawyer and with the authors comment clarifying that most of
the worst isn't "or later" it's safe to say it's not since one file
can't virally affect all the others.
It's a very thin line to walk on though.
Regards.
next prev parent reply other threads:[~2013-02-04 23:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 18:23 [Buildroot] [PATCH 01/10] bluez_utils: add license information Gustavo Zacarias
2013-01-29 18:23 ` [Buildroot] [PATCH 02/10] dialog: " Gustavo Zacarias
2013-01-29 22:20 ` Peter Korsgaard
2013-01-29 22:39 ` Gustavo Zacarias
2013-02-04 23:05 ` Peter Korsgaard
2013-02-04 23:30 ` Gustavo Zacarias [this message]
2013-01-29 18:23 ` [Buildroot] [PATCH 03/10] distcc: " Gustavo Zacarias
2013-01-29 22:22 ` Peter Korsgaard
2013-01-29 18:23 ` [Buildroot] [PATCH 04/10] gmpc: " Gustavo Zacarias
2013-01-29 22:23 ` Peter Korsgaard
2013-01-29 18:23 ` [Buildroot] [PATCH 05/10] libmpd: " Gustavo Zacarias
2013-01-29 22:24 ` Peter Korsgaard
2013-01-29 18:23 ` [Buildroot] [PATCH 06/10] tn5250: " Gustavo Zacarias
2013-01-29 22:25 ` Peter Korsgaard
2013-01-29 18:23 ` [Buildroot] [PATCH 07/10] libungif: " Gustavo Zacarias
2013-01-29 22:26 ` Peter Korsgaard
2013-01-29 18:23 ` [Buildroot] [PATCH 08/10] liboping: " Gustavo Zacarias
2013-01-29 22:29 ` Peter Korsgaard
2013-01-29 22:37 ` Gustavo Zacarias
2013-02-04 23:01 ` Peter Korsgaard
2013-02-05 7:44 ` Peter Korsgaard
2013-01-29 18:23 ` [Buildroot] [PATCH 09/10] kismet: " Gustavo Zacarias
2013-01-29 22:30 ` Peter Korsgaard
2013-01-29 18:23 ` [Buildroot] [PATCH 10/10] wipe: " Gustavo Zacarias
2013-01-29 22:31 ` Peter Korsgaard
2013-01-29 22:19 ` [Buildroot] [PATCH 01/10] bluez_utils: " 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=511044AF.8080700@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