git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pau Garcia i Quiles" <pgquiles@elpauer.org>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: git to libgit2 code relicensing
Date: Sat, 15 Nov 2008 11:28:39 +0100	[thread overview]
Message-ID: <3af572ac0811150228k291b8850idc34cb474f455aa7@mail.gmail.com> (raw)
In-Reply-To: <491EA1CC.9020605@op5.se>

> Shawn posted the exact text. The spirit of that license is that anyone can
> use an unmodified version of the library for whatever they want, but it's
> illegal to link non-GPL software to an altered version of the library. That
> is, the git community will get all changes back while other projects can
> use the official version of the library without having to worry about
> licensing issues. EvilCompany cannot make changes to the library and then
> link non-GPL'd software to their changed version. They can do that if they
> send their library changes upstream and then only use them once they're
> considered "official" though.

Do you mean if I write a patch to libgit2, send it upstream and make
it public on my website but it is not accepted upstream, I cannot link
my modified libgit2 version (i. e. libgit2 + my patch) to my non-GPL
software? It looks insane to me: I wrote the patch and made it public
but you guys did not accept it!

--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)

  reply	other threads:[~2008-11-15 10:29 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
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 [this message]
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=3af572ac0811150228k291b8850idc34cb474f455aa7@mail.gmail.com \
    --to=pgquiles@elpauer.org \
    --cc=git@vger.kernel.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).