From: ng0 <contact.ng0@cryptolab.net>
To: Marius Bakke <mbakke@fastmail.com>, Kei Kebreau <kei@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: Fix the reducelcs license
Date: Tue, 31 Jan 2017 17:38:32 +0000 [thread overview]
Message-ID: <87inovm8o7.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87k29byz01.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
Marius Bakke <mbakke@fastmail.com> writes:
> Kei Kebreau <kei@openmailbox.org> writes:
>
>> contact.ng0@cryptolab.net writes:
>>
>>> If I am not wrong: When no "Version 3 only" is specified, it is always
>>> "and later".
>>
>> Is there text in the GPL3 that says this? I was under the impression
>> that the "or any later version" clause had to be specified
>> explicitly. It doesn't help that there aren't any file headers to clear
>> this up.
>
> My understanding is that downstream users are free to use the "or later"
> clause if nothing else is specified. Say, if you copy parts of GPL3 code
> with no "or later" headers into your GPL3+ code.
>
> So distros need to distinguish the cases that are explicitly not "or any
> later version", but not impose other restrictions on the users.
>
> If that makes sense. But IANAL etc..
Okay, this makes sense.
I will mark the patch as done, doesn't need to be applied.
Thanks!
--
ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-01-31 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 11:32 Fix the reducelcs license contact.ng0
2017-01-31 11:32 ` [PATCH] gnu: reducelcs: Correct license contact.ng0
2017-01-31 15:02 ` Fix the reducelcs license Kei Kebreau
2017-01-31 16:29 ` Marius Bakke
2017-01-31 17:38 ` ng0 [this message]
2017-02-01 22:18 ` Ludovic Courtès
2017-02-01 23:56 ` ng0
2017-02-02 0:54 ` Kei Kebreau
2017-02-02 10:39 ` Hartmut Goebel
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=87inovm8o7.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
--cc=kei@openmailbox.org \
--cc=mbakke@fastmail.com \
/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.