git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: David Brown <git@davidb.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andreas Ericsson <ae@op5.se>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git to libgit2 code relicensing
Date: Sat, 15 Nov 2008 03:04:29 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0811150256140.27509@xanadu.home> (raw)
In-Reply-To: <20081115050039.GC2932@spearce.org>

On Fri, 14 Nov 2008, Shawn O. Pearce wrote:

> David Brown <git@davidb.org> wrote:
> > On Fri, Nov 14, 2008 at 03:46:58PM -0800, Shawn O. Pearce wrote:
> >
> >> 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.)
> >
> > Is this license intended to allow static linking but forbid dynamic
> > linking into a non-GPL program?  It depends on how you interpret
> > "linked into a combined executable", but that sounds like it
> > intentionally excludes the dynamic case.
> 
> I don't know.  When I read it myself I assumed dynamic linking
> would also be OK.

libgcc is a dynamic library on most modern systems these days. Yet they 
routinely execute non-GPL programs. If that text intentionally excluded 
the dynamic case then every non-GPL applications on such systems would 
have been breaking the license for a long time.  So I don't think anyone 
could have substance for such a claim.


Nicolas

  reply	other threads:[~2008-11-15  8:07 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
2008-11-15  4:30     ` David Brown
2008-11-15  5:00       ` Shawn O. Pearce
2008-11-15  8:04         ` Nicolas Pitre [this message]
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=alpine.LFD.2.00.0811150256140.27509@xanadu.home \
    --to=nico@cam.org \
    --cc=ae@op5.se \
    --cc=git@davidb.org \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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).