git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tay Ray Chuan <rctay89@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Mike Hommey <mh@glandium.org>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	Eric Wong <normalperson@yhbt.net>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Jeff King <peff@peff.net>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Git List <git@vger.kernel.org>
Subject: Re: GSoC 2010
Date: Fri, 12 Feb 2010 17:34:52 +0800	[thread overview]
Message-ID: <be6fef0d1002120134p7dda53e4h7c970bd852e6ce99@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.1002121034320.20986@pacific.mpi-cbg.de>

Hi,

On Fri, Feb 12, 2010 at 5:35 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Fri, 12 Feb 2010, Mike Hommey wrote:
>
>> On Fri, Feb 12, 2010 at 10:03:43AM +0100, Sverre Rabbelier wrote:
>>
>> > On Fri, Feb 12, 2010 at 10:02, Johannes Schindelin
>> > <Johannes.Schindelin@gmx.de> wrote:
>> > > Would it not make sense to implement git-remote-svn as a C program?
>> > > That should help matters especially on Windows, where git-svn is
>> > > very slow due to its using MSys (which is a stripped-down Cygwin, as
>> > > you know, jumping through hoops to bring some POSIX-iness to
>> > > Windows).
>> >
>> > It would very much be sense to do so, perhaps we should update the
>> > wiki to say that implementing it in C is strongly preferred?
>>
>> It is already mentioned on the wiki that this would probably be a
>> problem, license-wise. (the svn library is Apache license, which is
>> incompatible with GPLv2)
>
> So git-remote-svn would have to be under an Apache-compatible license, so
> what? It is not as if git-remote-svn was a derivative work of Git, just
> because it abides by a very simple command-line interface that happens to
> be defined in Git, but would work anywhere else, too.

hmm, what about distribution? Will we be able to distribute this
remote helper with the rest of Git's GPL-ed code?

As a side note, if I'm remember correctly, there used to be a
implementation of SHA-1 hashing algorithm from Mozilla  - was that
under MPL? If so, how did we deal with that? (Wikipedia says MPL is
incompatible with GPL, too.)

-- 
Cheers,
Ray Chuan

  parent reply	other threads:[~2010-02-12  9:34 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 20:23 GSoC 2010 Sverre Rabbelier
2010-02-11 21:48 ` Petr Baudis
2010-02-12  4:02   ` Christian Couder
     [not found]     ` <e72faaa81002120222p19db9c75u737e2615c14930b1@mail.gmail.com>
     [not found]       ` <e72faaa81002120226y5e4b1c28tbaf6a7dccb9634dc@mail.gmail.com>
2010-02-12 10:56         ` web-based client for Git, was " Johannes Schindelin
2010-02-12 11:04           ` Pau Garcia i Quiles
2010-02-12 11:20             ` Johannes Schindelin
2010-02-12 11:35           ` Petr Baudis
     [not found]             ` <e72faaa81002120355t4c8596d0q66da4aeb4cce3a94@mail.gmail.com>
2010-02-12 11:58               ` Pavan Kumar Sunkara
2010-02-12 12:18               ` Petr Baudis
2010-02-12 12:24                 ` Pavan Kumar Sunkara
2010-02-12 12:33                   ` Petr Baudis
2010-02-12 12:44                 ` Mike Hommey
2010-02-12 12:51                   ` Petr Baudis
2010-02-12 12:54                     ` Pavan Kumar Sunkara
2010-02-12 13:07                       ` Johannes Schindelin
2010-02-12 13:05                         ` Petr Baudis
2010-02-12 13:07                           ` Pavan Kumar Sunkara
2010-02-12 13:15                           ` Johannes Schindelin
2010-02-12 13:30                           ` Jakub Narebski
2010-02-12 13:03                     ` Mike Hommey
2010-02-12 18:24                     ` david
2010-02-12 15:14                 ` Scott Chacon
2010-02-12 16:45                   ` Petr Baudis
2010-02-12 16:52                     ` Jan Koprowski
2010-02-12 17:01                       ` Pavan Kumar Sunkara
2010-02-12  8:06 ` Eric Wong
2010-02-12  9:02   ` Johannes Schindelin
2010-02-12  9:03     ` Sverre Rabbelier
2010-02-12  9:16       ` Mike Hommey
2010-02-12  9:35         ` Johannes Schindelin
2010-02-12  9:32           ` Sverre Rabbelier
2010-02-12 10:07             ` Mike Hommey
2010-02-12 10:49               ` strbuf & other stuff dual-licensing, was " Johannes Schindelin
2010-02-12 16:10             ` Daniel Barkalow
2010-02-12 16:41               ` Sverre Rabbelier
2010-02-12 19:16                 ` Daniel Barkalow
2010-02-12 19:30                   ` Sverre Rabbelier
2010-02-12 19:47                     ` Scott Chacon
2010-02-12  9:34           ` Tay Ray Chuan [this message]
2010-02-12  9:52             ` Sverre Rabbelier
2010-02-12  9:30       ` Johannes Schindelin
2010-02-12  9:06   ` Sverre Rabbelier
2010-02-12 16:19 ` Daniel Barkalow
2010-02-12 16:43   ` Sverre Rabbelier
2010-02-14  6:52 ` Jeff King
2010-02-14 18:15   ` Johannes Schindelin
2010-02-15  8:30     ` Jeff King
2010-02-15 16:53       ` Shawn O. Pearce
2010-02-15 21:53         ` Sverre Rabbelier
2010-02-15 22:33           ` Johannes Schindelin
2010-02-15 22:31             ` Sverre Rabbelier
2010-02-15 22:36               ` Shawn O. Pearce
2010-02-15 22:58                 ` Sverre Rabbelier

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=be6fef0d1002120134p7dda53e4h7c970bd852e6ce99@mail.gmail.com \
    --to=rctay89@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=mh@glandium.org \
    --cc=normalperson@yhbt.net \
    --cc=peff@peff.net \
    --cc=spearce@spearce.org \
    --cc=srabbelier@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).