From: Nicolas Pitre <nico@cam.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Daniel Barkalow <barkalow@iabervon.org>,
Robin Rosenberg <robin.rosenberg@dewire.com>,
Dave Watson <dwatson@mimvista.com>,
Philippe Ombredanne <philippe@easyeclipse.org>,
git@vger.kernel.org
Subject: Re: Java Git (aka jgit) library switching license to BSD/EPL
Date: Fri, 09 May 2008 12:26:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805091214170.23581@xanadu.home> (raw)
In-Reply-To: <20080509021158.GA29038@spearce.org>
On Thu, 8 May 2008, Shawn O. Pearce wrote:
> Nico, Linus, Junio, Daniel, Dscho, et.al.:
>
> We would appreciate it if you could provide a statement saying
> you have no current copyright ownership interest in jgit, and that
> you do not currently own nor invented any patents related to the
> "Git technology" that this code might need to use to function as
> a Git implementation.
I do not have any such copyright nor patent claims for the jgit code.
As long as the C version remains the authoritative reference
implementation for protocol and data format, and any algorithmic
improvements made to the jgit source can be merged back into the C
version using the GPL, then I have no issue with the license used by
jgit either.
Nicolas
next prev parent reply other threads:[~2008-05-09 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 2:11 Java Git (aka jgit) library switching license to BSD/EPL Shawn O. Pearce
2008-05-09 2:29 ` Dave Watson
2008-05-09 3:05 ` Daniel Barkalow
2008-05-09 7:20 ` Robin Rosenberg
2008-05-09 9:57 ` Johannes Schindelin
2008-05-09 16:26 ` Nicolas Pitre [this message]
2008-05-09 23:38 ` Shawn O. Pearce
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.1.10.0805091214170.23581@xanadu.home \
--to=nico@cam.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=dwatson@mimvista.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=philippe@easyeclipse.org \
--cc=robin.rosenberg@dewire.com \
--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).