Re: git fast-import/fast-export
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Mar 6, 2010, 15:29 UTC
- Message-ID
- <alpine.DEB.1.00.1003061623511.7596@pacific.mpi-cbg.de>
- In-Reply-To
- <fabb9a1e1003060702r671b57f4m9308863f566d5fbd@mail.gmail.com>
Hi,
On Sat, 6 Mar 2010, Sverre Rabbelier wrote:
Show 18 quoted lines
> As you can read on the wiki [0] I am hoping to mentor a GSoC student > this year to work on git-remote-svn, a remote-helper for svn implemented > in C. If successful git will be able to work natively with svn > repositories, no offense to Eric, but git-svn is a tad sub-optimal ;). > To do this I think the best way to go forward is to implement the helper > by hooking up a fast-import/fast-export frontend to libsvn. Since it > will be implemented in C (partially for speed, but also so that it will > be usable on Windows as well), the current fast-import.c and > builtin-fast-export.c could be of great use. Neither files have an > explicit license, (although builtin-fast-import.c says copyright by > Dscho) which puts them under the GPLv2. The libsvn bindings are apache > licensed, so we need something licensed either under the apache license, > or something compatible with that. > > So my question, would it be possible to relicense fast-import.c and > builtin-fast-export.c under "GPLv2 or later" instead of the current > "GPLv2"? That way we can use (parts of) the code in the svn helper, > which will (probably) be licensed as "GPLv2 or later" as well.
Sure, as far as my parts go, I am fine even with BSD.
Unfortunately, git shortlog shows 18 different authors for fast-export, and blame still shows 17 surviving. I fear you have to ask them all.
The situation is worse with fast-import, with 40 and 36 authors, respectively.
Ciao,