From: Shawn Pearce <spearce@spearce.org>
To: Wolfgang Denk <wd@denx.de>
Cc: Jon Smirl <jonsmirl@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Licensing and the library version of git
Date: Fri, 28 Jul 2006 01:04:45 -0400 [thread overview]
Message-ID: <20060728050444.GA30783@spearce.org> (raw)
In-Reply-To: <20060727195614.7EDAE353B04@atlas.denx.de>
Wolfgang Denk <wd@denx.de> wrote:
> In message <9e4733910607270554p5622ee20ida8c264cf3122500@mail.gmail.com> you wrote:
> >
> > I see that someone is already writing a pure Java version which will
> > work around the GPL problem assuming the Java version is released
> > under a compatible license.
>
> ... and assuming it is a clean-room implementation which does not
> borrow from the GPL code.
Heh. This is actually possibly a problem.
I'm the person developing the Java implementation.
I've seen some of the core GIT code. The reflog implementation is my
most notable contribution, but I've seen other things in there too.
Most of the Java code is quite different from the C code; the
largest common component is the pack delta decompressor. I ran it
past Nico as he wrote the C version. He didn't seem to think that
the Java version was derived from the C version.
The issue there really was that the pack file format wasn't
completely documented external from the code (I actually found a
bug in the docs and submitted a patch to correct it) and the delta
format is definately not documented so I had to dig around in the
C code to figure it out. On the other hand the commit format,
tree format and the loose object header were all clearly self
describing so I didn't need to go digging through the source to
figure out how to parse (or generate) them.
So yes, the Java implementation is derived from the C
(GPL'd!) implementation, but also no, its not...
I think its going to really just come down to a list consensus.
If Linus, Junio, Nico, et.al. think that my Java version is too
derived from the C GPL'd implementation to be released under any
license other than the GPL then I'll probably just abandon the code
line entirely, as the GPL is incompatible with the Sun JRE runtime
lirbary. On the other hand its probably going to be released under
the IBM Common Public License or the Apache License.
--
Shawn.
next prev parent reply other threads:[~2006-07-28 5:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 21:36 Licensing and the library version of git Jon Smirl
2006-07-27 1:40 ` Shawn Pearce
2006-07-27 11:41 ` Petr Baudis
2006-07-27 12:02 ` Johannes Schindelin
2006-07-27 12:54 ` Jon Smirl
2006-07-27 13:11 ` Petr Baudis
2006-07-27 16:11 ` Jon Smirl
[not found] ` <Pine.LNX.4.64 .0607270936200.4168@g5.osdl.org>
2006-07-27 16:38 ` Johannes Schindelin
2006-07-27 16:41 ` Linus Torvalds
2006-07-27 16:46 ` Linus Torvalds
2006-07-27 16:58 ` Jakub Narebski
2006-07-27 17:47 ` Jon Smirl
2006-07-28 0:25 ` Anand Kumria
2006-07-27 16:51 ` Grzegorz Kulewski
2006-07-27 17:07 ` Linus Torvalds
2006-07-27 19:31 ` Daniel Barkalow
2006-07-27 20:41 ` Johannes Schindelin
2006-07-27 18:42 ` David Lang
2006-07-27 19:44 ` Linus Torvalds
2006-07-27 19:49 ` David Lang
2006-07-27 20:38 ` Johannes Schindelin
2006-07-28 0:24 ` Anand Kumria
2006-07-28 0:43 ` Jon Smirl
2006-07-28 9:01 ` Johannes Schindelin
2006-07-27 14:04 ` Johannes Schindelin
2006-07-27 17:20 ` Petr Baudis
2006-07-27 17:23 ` Petr Baudis
2006-07-27 17:44 ` Linus Torvalds
2006-07-27 19:56 ` Wolfgang Denk
2006-07-27 20:39 ` Johannes Schindelin
2006-07-27 20:51 ` Petr Baudis
2006-07-27 21:06 ` Johannes Schindelin
2006-07-27 21:10 ` Wolfgang Denk
2006-07-27 21:16 ` Johannes Schindelin
2006-07-27 21:15 ` Linus Torvalds
2006-07-27 21:19 ` Johannes Schindelin
2006-07-28 5:04 ` Shawn Pearce [this message]
2006-07-28 8:44 ` Johannes Schindelin
2006-07-29 3:56 ` Shawn Pearce
2006-07-29 4:31 ` Jon Smirl
2006-07-29 11:21 ` Johannes Schindelin
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=20060728050444.GA30783@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=wd@denx.de \
/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).