From: Andreas Ericsson <ae@op5.se>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git to libgit2 code relicensing
Date: Sun, 16 Nov 2008 12:50:44 +0100 [thread overview]
Message-ID: <49200914.6090506@op5.se> (raw)
In-Reply-To: <200811151615.42345.chriscool@tuxfamily.org>
Christian Couder wrote:
> Hi Andreas,
>
> Le vendredi 14 novembre 2008, Andreas Ericsson a écrit :
>> I've been working quite a lot on git -> libgit2 code moving,
>
> It would be nice if there was somewhere on the web where your work could be
> seen. If there is already, could you send (or resend) the URL? This way
> people might have look and perhaps even help you. (Though I don't promise
> anything as I have already a lot of things on my TODO list.) Thanks in
> advance.
>
When I was about to, I realized these licensing issues actually made it
illegal to do so without getting the permissions from the involved authors.
Now that Linus and a lot of other core contributors have given their consent,
I'll be able to start re-ordering the commits so I can publish those parts
originating from consenting authors while holding off on those that I can't
tell for sure are ok with it. Legal issues are no fun what so ever.
>> but the licensing stuff is a bit depressing, as I can't know
>> if the work I'm doing is for nothing or not.
>>
>> The license decided for libgit2 is "GPL with gcc exception".
>> Those who are OK with relicensing their contributions under
>> that license for the purpose of libgit2, can you please say
>> so?
>
> It's ok to relicense my git related work under the "GPL with gcc exception"
> license.
>
Thank you. With the current list of ok's 73.09% of the code in git.git
seems to be relicenseable for the purpose of libgit2. That will provide
quite a kickstart.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-11-16 11:52 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
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 [this message]
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=49200914.6090506@op5.se \
--to=ae@op5.se \
--cc=chriscool@tuxfamily.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 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.