git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Ericsson <ae@op5.se>, Git Mailing List <git@vger.kernel.org>
Subject: Re: git to libgit2 code relicensing
Date: Fri, 14 Nov 2008 15:46:58 -0800	[thread overview]
Message-ID: <20081114234658.GA2932@spearce.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0811141512480.3468@nehalem.linux-foundation.org>

Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Fri, 14 Nov 2008, Andreas Ericsson wrote:
> > 
> > The license decided for libgit2 is "GPL with gcc exception".
> 
> What's the exact language? 
> 
> I'm likely ok with GPLv2 + libgcc-like exception, but I'd like to see the 
> exact one. I haven't followed the discussions much..

The language we are using in libgit2 is taken from libgcc, and is
as follows:

--8<--

 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.

 In addition to the permissions in the GNU General Public License,
 the authors give you unlimited permission to link the compiled
 version of this file into combinations with other programs,
 and to distribute those combinations without any restriction
 coming from the use of this file.  (The General Public License
 restrictions do apply in other respects; for example, they cover
 modification of the file, and distribution when not linked into
 a combined executable.)

----------------------------------------------------------------------

		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991

(... the rest of GPL v2 as it appears in git.git ...)

-- 
Shawn.

  reply	other threads:[~2008-11-14 23:48 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 20:59 git to libgit2 code relicensing Andreas Ericsson
2008-11-14 21:33 ` Martin Koegler
2008-11-14 21:46   ` Sverre Rabbelier
2008-11-14 22:57     ` Andreas Ericsson
2008-11-14 22:56   ` Andreas Ericsson
2008-11-15 17:13     ` Martin Koegler
2008-11-14 23:13 ` Linus Torvalds
2008-11-14 23:46   ` Shawn O. Pearce [this message]
2008-11-15  4:30     ` David Brown
2008-11-15  5:00       ` Shawn O. Pearce
2008-11-15  8:04         ` Nicolas Pitre
2008-11-15 18:39           ` David Brown
2008-11-15 12:39     ` Miklos Vajna
2008-11-15 13:00       ` Junio C Hamano
2008-11-15 19:33         ` Miklos Vajna
2008-11-15 22:12           ` Pierre Habouzit
2008-11-15 18:49       ` David Brown
2008-11-15 16:39     ` Linus Torvalds
2008-11-15 10:17   ` Andreas Ericsson
2008-11-15 10:28     ` Pau Garcia i Quiles
2008-11-15 11:05       ` Andreas Ericsson
2008-11-15 11:33         ` Pau Garcia i Quiles
2008-11-15 11:52           ` Andreas Ericsson
2008-11-15 18:53       ` David Brown
2008-11-16  1:30 ` Daniel Barkalow
     [not found] ` <200811151615.42345.chriscool@tuxfamily.org>
2008-11-16 11:50   ` Andreas Ericsson
2008-11-16 21:00     ` Johannes Schindelin
2008-11-16 21:09       ` Sverre Rabbelier
2008-11-17  7:24       ` Andreas Ericsson
2008-11-17 15:40         ` Shawn O. Pearce
2008-11-17 21:44           ` Andreas Ericsson
2008-11-20 17:41 ` René Scharfe
2008-11-25 15:19 ` Kristian Høgsberg

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=20081114234658.GA2932@spearce.org \
    --to=spearce@spearce.org \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).