From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] stress: fix download url
Date: Tue, 8 Oct 2013 17:48:02 +0200 [thread overview]
Message-ID: <20131008174802.2c023331@skate> (raw)
In-Reply-To: <874n8r7p1m.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Tue, 08 Oct 2013 17:36:21 +0200, Peter Korsgaard wrote:
> The new tarball has a bunch of binary .-files, and COPYING is GPL3
> instead of GPL2:
>
> diff -u 1/stress-1.0.4/COPYING 2/stress-1.0.4/COPYING|head /tmp/i
> --- 1/stress-1.0.4/COPYING 2010-03-19 08:21:09.000000000 +0100
> +++ 2/stress-1.0.4/COPYING 2010-03-24 00:34:05.000000000 +0100
> @@ -1,622 +1,281 @@
> GNU GENERAL PUBLIC LICENSE
> - Version 3, 29 June 2007
> + Version 2, June 1991
>
> - Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
> + Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
> + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
>
You mean the new tarball has a GPLv2 COPYING instead of GPLv3. This was
precisely was originally triggered the discussion: the package source
code and web site was saying GPLv2, but the COPYING was saying GPLv3.
Axel contacted the author, who replaced the COPYING by a GPLv2 one,
which is ok.
Obviously, all the other files look strange, but the COPYING change is
intentional.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-08 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 2:43 [Buildroot] [PATCH 1/2] stress: fix download url Axel Lin
2013-10-08 2:46 ` [Buildroot] [PATCH 2/2] stress: add license information Axel Lin
2013-10-08 7:15 ` Thomas Petazzoni
2013-10-08 7:44 ` Axel Lin
2013-10-08 15:36 ` [Buildroot] [PATCH 1/2] stress: fix download url Peter Korsgaard
2013-10-08 15:48 ` Thomas Petazzoni [this message]
2013-10-08 20:06 ` Peter Korsgaard
2013-10-08 20:19 ` 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=20131008174802.2c023331@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.