git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Roger C. Soares" <rogersoares@intelinet.com.br>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Martin Langhoff <martin.langhoff@gmail.com>,
	Chris Frey <cdfrey@foursquare.net>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	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: Fri, 30 May 2008 09:07:13 -0300	[thread overview]
Message-ID: <483FEDF1.7010308@intelinet.com.br> (raw)
In-Reply-To: <20080529041901.GA12896@spearce.org>


Shawn O. Pearce escreveu:
> "Roger C. Soares" <rogersoares@intelinet.com.br> wrote:
>   
>> Martin Langhoff escreveu:
>>     
>>> On Tue, May 27, 2008 at 11:44 AM, Shawn O. Pearce <spearce@spearce.org> 
>>> wrote:
>>>  
>>>       
>>>> So in all time these users have added a total of 14 lines between
>>>> them.  Out of 122,576 total added lines.  It amounts to only 0.011%
>>>> of the total contribution.  In the US a change this small may not
>>>> even be copyrightable.
>>>>    
>>>>         
>>> It'd be nice to hear from them, but I looks fair to me to say that
>>> those contributors - while very valuable - cannot hold the project
>>> back.
>>>       
>> Well, FWIW I'm ok with the license change.
>>     
>
> Heh, thanks for chiming in Roger.  We're likely to start talking
> about moving egit to 100% EPL soon too.  I think your contribution
> there is quite non-trivial, so we'll certainly need your blessing
> for that.  :-)
>   
Hi Shawn, Robin told me about it and asked for permission some time ago, 
so my permission is given already. Anyway, I can confirm this later if 
necessary. :)

[]s,
Roger.

  reply	other threads:[~2008-05-30 12:09 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 [this message]
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=483FEDF1.7010308@intelinet.com.br \
    --to=rogersoares@intelinet.com.br \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=cdfrey@foursquare.net \
    --cc=dwatson@mimvista.com \
    --cc=git@vger.kernel.org \
    --cc=laforge@gnumonks.org \
    --cc=marek.zawirski@gmail.com \
    --cc=martin.langhoff@gmail.com \
    --cc=robin.rosenberg@dewire.com \
    --cc=spearce@spearce.org \
    --cc=vegard.nossum@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).