From: "Florian Köberle" <FloriansKarten@web.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Robin Rosenberg <robin.rosenberg@dewire.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] Java Git (aka jgit) has switched to 3-clause BSD
Date: Tue, 27 May 2008 14:11:57 +0200 [thread overview]
Message-ID: <483BFA8D.30309@web.de> (raw)
In-Reply-To: <20080526044640.GB30245@spearce.org>
Hi Shawn
will you convert my last patches (v3) too, or do I have to do it manually?
It would be cool if you would accept or comment my last patches.
Best regards,
Florian
Shawn O. Pearce 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.
>
> The change is here:
>
> git://repo.or.cz/egit/spearce.git bsd
>
> and is based upon the the thread that I started on this list:
>
> http://article.gmane.org/gmane.comp.version-control.git/81585
>
> If there are no objections within the next couple of days we'll
> merge it to the main tree.
>
next prev parent reply other threads:[~2008-05-27 12:12 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
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 [this message]
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=483BFA8D.30309@web.de \
--to=florianskarten@web.de \
--cc=git@vger.kernel.org \
--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).