From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add mtd-utils.
Date: Fri, 02 Sep 2016 14:49:27 +0200 [thread overview]
Message-ID: <87poomlb54.fsf@gnu.org> (raw)
In-Reply-To: <877fau4u0l.fsf@gmail.com> (Alex Kost's message of "Fri, 02 Sep 2016 10:53:46 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Ludovic Courtès (2016-09-01 15:13 +0300) wrote:
>
>> Danny Milosavljevic <dannym@scratchpost.org> skribis:
>>
>>> On Wed, 31 Aug 2016 22:59:11 +0200
>>> ludo@gnu.org (Ludovic Courtès) wrote:
>>>
>>>> Are there GPLv2 license headers that lack the “or any later version”
>>>> wording, or anything that explicitly says “version 2 only”? If not,
>>>> it’s v2-or-later.
>>
>> [...]
>>
>>> ./mkfs.ubifs/crc16.h: ' * Implements the standard CRC-16: * Width 16 *
>>> Poly 0x8005 ( x^16 + x^15 + x^2 + 1 ) * Init 0 * * Copyright ( c )
>>> 2005 Ben Gardner <bgardner@wabtec.com> * * This code was taken from
>>> the linux kernel. The license is GPL Version 2. '
>>
>> OK, GPLv2-only!
>
> Wait, why? There are files that have a full license headers with "or
> any later version", for example "docfdisk.c", "flash_erase.c" and
> others. That's why I thought both gpl2 and gpl2+ should be listed.
But they are combined, so the combined work, which is what we (should)
care about, is ‘gpl2’.
At least that’s how I usually do it, but I agree that this is an
undocumented convention that’s probably not unanimously followed.
Ludo’.
prev parent reply other threads:[~2016-09-02 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 23:24 [PATCH] gnu: Add mtd-utils Danny Milosavljevic
2016-08-30 8:08 ` Alex Kost
2016-08-30 8:39 ` Danny Milosavljevic
2016-08-31 7:24 ` Alex Kost
2016-08-31 20:59 ` Ludovic Courtès
2016-08-31 21:39 ` Danny Milosavljevic
2016-09-01 12:13 ` Ludovic Courtès
2016-09-02 7:53 ` Alex Kost
2016-09-02 8:07 ` Alex Vong
2016-09-02 12:49 ` Ludovic Courtès [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=87poomlb54.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.