From: Sam Vilain <sam@vilain.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] doc: add clarification of existing GPLv2 license terms to manual pages
Date: Fri, 24 Mar 2006 11:18:06 +1200 [thread overview]
Message-ID: <44232CAE.2040102@vilain.net> (raw)
In-Reply-To: <20060323215759.GW18185@pasky.or.cz>
Petr Baudis wrote:
> Dear diary, on Thu, Mar 23, 2006 at 02:58:50AM CET, I got a letter
> where Sam Vilain <sam.vilain@catalyst.net.nz> said that...
>
>>The GPLv3 is less ambiguous on these things, but a decision on the use
>>of GPLv3 has already been deferred.
>
>
> Was it?
>
> My fulltext =git mailbox search doesn't yield any matches at all.
I refer to this section from COPYING:
Note that the only valid version of the GPL as far as this project
is concerned is _this_ particular version of the license (ie v2, not
v2.2 or v3.x or whatever), unless explicitly otherwise stated.
HOWEVER, in order to allow a migration to GPLv3 if that seems like
a good idea, I also ask that people involved with the project make
their preferences known. In particular, if you trust me to make that
decision, you might note so in your copyright message, ie something
like
This file is licensed under the GPL v2, or a later version
at the discretion of Linus.
might avoid issues. But we can also just decide to synchronize and
contact all copyright holders on record if/when the occasion arises.
Linus Torvalds
This may become problematic if any of the copyright holders start
becoming Old Ones or otherwise not being contactable...
Sam.
prev parent reply other threads:[~2006-03-23 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 1:58 [PATCH] doc: add clarification of existing GPLv2 license terms to manual pages Sam Vilain
2006-03-23 2:02 ` Sam Vilain
2006-03-23 21:57 ` Petr Baudis
2006-03-23 23:18 ` Sam Vilain [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=44232CAE.2040102@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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.