git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Robin Rosenberg" <robin.rosenberg@dewire.com>,
	"Dave Watson" <dwatson@mimvista.com>,
	"Marek Zawirski" <marek.zawirski@gmail.com>,
	git@vger.kernel.org, laforge@gnumonks.org
Subject: Re: [ANNOUNCE] Java Git (aka jgit) has switched to 3-clause BSD
Date: Mon, 26 May 2008 10:13:45 +0200	[thread overview]
Message-ID: <19f34abd0805260113w1341a26bg140d1dbb7438bf46@mail.gmail.com> (raw)
In-Reply-To: <20080526044640.GB30245@spearce.org>

Hi,

On Mon, May 26, 2008 at 6:46 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
> As of 53a2cc3 the jgit library (a 100% pure Java implementation
> of git) is now licensed under a 3-clause (new-style) BSD license.
> The change was done with a Perl script to rewrite all source code
> headers within the org.spearce.jgit package.  Copyright information
> was updated based upon the output of git-blame.

I previously read about this transition from GPL to BSD.

IANAL, but isn't the current version a derivative of the older
version, meaning that you need to take all authors into account when
doing this switch, and not just the authors of the _current_ code?

(Or did you get a consent from all previous authors as well as current authors?)


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  reply	other threads:[~2008-05-26  8:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26  4:46 [ANNOUNCE] Java Git (aka jgit) has switched to 3-clause BSD Shawn O. Pearce
2008-05-26  8:13 ` Vegard Nossum [this message]
2008-05-26 10:08   ` Johannes Schindelin
2008-05-26 11:22     ` Vegard Nossum
2008-05-26 11:32       ` Johannes Schindelin
2008-05-26 18:12       ` Chris Frey
2008-05-26 23:44         ` Shawn O. Pearce
2008-05-27  0:13           ` Martin Langhoff
2008-05-27 22:27             ` Roger C. Soares
2008-05-29  4:19               ` Shawn O. Pearce
2008-05-30 12:07                 ` Roger C. Soares
2008-05-27  9:14           ` Jakub Narebski
2008-05-27 12:11 ` Florian Köberle
2008-05-28 23:26   ` Shawn O. Pearce
2008-06-07 11:03 ` Robin Rosenberg
2008-06-07 16:02   ` Shawn O. Pearce
2008-06-09 19:39 ` Robin Rosenberg
2008-06-10  2:15   ` Philippe Ombredanne

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=19f34abd0805260113w1341a26bg140d1dbb7438bf46@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=dwatson@mimvista.com \
    --cc=git@vger.kernel.org \
    --cc=laforge@gnumonks.org \
    --cc=marek.zawirski@gmail.com \
    --cc=robin.rosenberg@dewire.com \
    --cc=spearce@spearce.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).