git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Scott Chacon <schacon@gmail.com>
Cc: git list <git@vger.kernel.org>, Andreas Ericsson <ae@op5.se>
Subject: Re: re-licensing pkt-line.c code
Date: Thu, 25 Sep 2008 11:01:25 -0700	[thread overview]
Message-ID: <20080925180125.GS3669@spearce.org> (raw)
In-Reply-To: <48DBD114.80805@op5.se>

Andreas Ericsson <ae@op5.se> wrote:
> Scott Chacon wrote:
>>
>> There are about 20-25 lines of code from pkt-line.c that I think were
>> originally written back in 2005 that I would like to use [...]
>>
>> I have to relicense this, since I can't legally distribute my source
>> code for the iphone app due to Apples f**king NDA.  I would like to
>> release my ObjectiveGit project under the MIT (or, alternately, LGPL).
>
>>  I could come up with an alternate way to
>> accomplish the same thing, but it seems like a waste of time to do so,
>> and helpful to nobody.
>
> Well, tracking down the original author(s) could turn out to be harder.

Its already cost more time to ask for permission to reuse these
20-25 lines of code than it would take to figure out how to write
it yourself, and code it.  And Linus still hasn't had a chance to
chime in on this thread.

My guess is you aren't going to get approval from him to relicense
his code.  But he doesn't hold a monopoly on int->hex conversion
algorithms so you should be able to implement something that produces
the same results, given the same inputs, and not have him sue you
in some Utah court.

-- 
Shawn.

      reply	other threads:[~2008-09-25 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25 17:17 re-licensing pkt-line.c code Scott Chacon
2008-09-25 17:49 ` Implementations of Git (was: re-licensing pkt-line.c code) Jakub Narebski
2008-09-26 11:42   ` git-sharp, was " Johannes Schindelin
2008-09-25 17:57 ` re-licensing pkt-line.c code Andreas Ericsson
2008-09-25 18:01   ` Shawn O. Pearce [this message]

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=20080925180125.GS3669@spearce.org \
    --to=spearce@spearce.org \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=schacon@gmail.com \
    /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).