{"thread":{"id":"22929","subject":"Re: git fast-import/fast-export","startedAt":"2010-03-06T15:02:18Z","lastAt":"2010-03-06T21:45:42Z","messageCount":6,"participants":["Shawn O. Pearce","Johannes Schindelin","Sverre Rabbelier","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"136335","messageId":"fabb9a1e1003060702r671b57f4m9308863f566d5fbd@mail.gmail.com","threadId":"22929","inReplyTo":null,"subject":"git fast-import/fast-export","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-03-06T15:02:18Z","receivedAt":"2010-03-06T15:02:18Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nAs you can read on the wiki [0] I am hoping to mentor a GSoC student\nthis year to work on git-remote-svn, a remote-helper for svn\nimplemented in C. If successful git will be able to work natively with\nsvn repositories, no offense to Eric, but git-svn is a tad sub-optimal\n;). To do this I think the best way to go forward is to implement the\nhelper by hooking up a fast-import/fast-export frontend to libsvn.\nSince it will be implemented in C (partially for speed, but also so\nthat it will be usable on Windows as well), the current fast-import.c\nand builtin-fast-export.c could be of great use. Neither files have an\nexplicit license, (although builtin-fast-import.c says copyright by\nDscho) which puts them under the GPLv2. The libsvn bindings are apache\nlicensed, so we need something licensed either under the apache\nlicense, or something compatible with that.\n\nSo my question, would it be possible to relicense fast-import.c and\nbuiltin-fast-export.c under \"GPLv2 or later\" instead of the current\n\"GPLv2\"? That way we can use (parts of) the code in the svn helper,\nwhich will (probably) be licensed as \"GPLv2 or later\" as well.\n\n[0] http://git.wiki.kernel.org/index.php/SoC2010Ideas#A_remote_helper_for_svn\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"136323","messageId":"alpine.DEB.1.00.1003061623511.7596@pacific.mpi-cbg.de","threadId":"22929","inReplyTo":"fabb9a1e1003060702r671b57f4m9308863f566d5fbd@mail.gmail.com","subject":"Re: git fast-import/fast-export","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2010-03-06T15:29:24Z","receivedAt":"2010-03-06T15:29:24Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 6 Mar 2010, Sverre Rabbelier wrote:\n\n> As you can read on the wiki [0] I am hoping to mentor a GSoC student \n> this year to work on git-remote-svn, a remote-helper for svn implemented \n> in C. If successful git will be able to work natively with svn \n> repositories, no offense to Eric, but git-svn is a tad sub-optimal ;). \n> To do this I think the best way to go forward is to implement the helper \n> by hooking up a fast-import/fast-export frontend to libsvn. Since it \n> will be implemented in C (partially for speed, but also so that it will \n> be usable on Windows as well), the current fast-import.c and \n> builtin-fast-export.c could be of great use. Neither files have an \n> explicit license, (although builtin-fast-import.c says copyright by \n> Dscho) which puts them under the GPLv2. The libsvn bindings are apache \n> licensed, so we need something licensed either under the apache license, \n> or something compatible with that.\n> \n> So my question, would it be possible to relicense fast-import.c and \n> builtin-fast-export.c under \"GPLv2 or later\" instead of the current \n> \"GPLv2\"? That way we can use (parts of) the code in the svn helper, \n> which will (probably) be licensed as \"GPLv2 or later\" as well.\n\nSure, as far as my parts go, I am fine even with BSD.\n\nUnfortunately, git shortlog shows 18 different authors for fast-export, \nand blame still shows 17 surviving. I fear you have to ask them all.\n\nThe situation is worse with fast-import, with 40 and 36 authors, \nrespectively.\n\nCiao,\n"},{"id":"136331","messageId":"7v3a0di87z.fsf@alter.siamese.dyndns.org","threadId":"22929","inReplyTo":"fabb9a1e1003060702r671b57f4m9308863f566d5fbd@mail.gmail.com","subject":"Re: git fast-import/fast-export","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-03-06T19:02:56Z","receivedAt":"2010-03-06T19:02:56Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Sverre Rabbelier <srabbelier@gmail.com> writes:\n\n> ;). To do this I think the best way to go forward is to implement the\n> helper by hooking up a fast-import/fast-export frontend to libsvn.\n\nIsn't fast-import designed to be used as a downstream side of a pipe that\nis fed by an independent program you write (and may link with libsvn)?  It\nwouldn't care what license that data producer program is distributed under.\n\nOn the fast-export side the issue should ideally be the same.  Your new\nprogram that may link with libsvn reads from the datastream that comes\nfrom the git repository via pipe as an independent process to propagate\nthe changes to the subversion side.\n\nYou may need to have/keep additional info on commits for roundtrip, but\nthat is between the part of your program that feeds fast-import and the\nother part of your program that consumes the output from fast-export.\nfast-import may need to be told to export mark, and you pick them up to\nsee what commits resulted on the git side from what you fed it, and later\nuse that information when reading from fast-export to propagate new things\nback to subversion side.  No?\n"},{"id":"136329","messageId":"fabb9a1e1003061105u70cf87b8h579fe154a24fb8f0@mail.gmail.com","threadId":"22929","inReplyTo":"7v3a0di87z.fsf@alter.siamese.dyndns.org","subject":"Re: git fast-import/fast-export","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-03-06T19:05:22Z","receivedAt":"2010-03-06T19:05:22Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Sat, Mar 6, 2010 at 20:02, Junio C Hamano <gitster@pobox.com> wrote:\n> Isn't fast-import designed to be used as a downstream side of a pipe that\n> is fed by an independent program you write (and may link with libsvn)?  It\n> wouldn't care what license that data producer program is distributed under.\n\nYes, I'm not worried about using the 'git-fast-import' or the\n'git-fast-export' binary, I want to use-and-modify the parsing code to\nwork as a fast-import/fast-export frontend to svn _on top_ of using\nthose binaries..\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"136241","messageId":"20100306214321.GD2529@spearce.org","threadId":"22929","inReplyTo":"fabb9a1e1003061105u70cf87b8h579fe154a24fb8f0@mail.gmail.com","subject":"Re: git fast-import/fast-export","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2010-03-06T21:43:21Z","receivedAt":"2010-03-06T21:43:21Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Sverre Rabbelier <srabbelier@gmail.com> wrote:\n> On Sat, Mar 6, 2010 at 20:02, Junio C Hamano <gitster@pobox.com> wrote:\n> > Isn't fast-import designed to be used as a downstream side of a pipe that\n> > is fed by an independent program you write (and may link with libsvn)? ?It\n> > wouldn't care what license that data producer program is distributed under.\n> \n> Yes, I'm not worried about using the 'git-fast-import' or the\n> 'git-fast-export' binary, I want to use-and-modify the parsing code to\n> work as a fast-import/fast-export frontend to svn _on top_ of using\n> those binaries..\n\nOh.  Yuck.\n\nI guess I can give my blessing to relicense anything in fast-import\nthat I've written from GPLv2 to GPLv2 or v3.  But as Dscho points\nout, there are many authors in even the parsing code.  You will\nneed to get consent from all of them.\n\n-- \nShawn.\n"},{"id":"136333","messageId":"fabb9a1e1003061345t7e261505q27453ff546e5463b@mail.gmail.com","threadId":"22929","inReplyTo":"20100306214321.GD2529@spearce.org","subject":"Re: git fast-import/fast-export","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-03-06T21:45:42Z","receivedAt":"2010-03-06T21:45:42Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Sat, Mar 6, 2010 at 22:43, Shawn O. Pearce <spearce@spearce.org> wrote:\n> Oh.  Yuck.\n\nWhy is that a bad idea?\n\n> I guess I can give my blessing to relicense anything in fast-import\n> that I've written from GPLv2 to GPLv2 or v3.\n\nOk, if nothing else we can use one of the earlier versions ;).\n\n> But as Dscho points\n> out, there are many authors in even the parsing code.  You will\n> need to get consent from all of them.\n\nRight, I figured I'd first get an OK from the top N before spamming 40\npeople :).\n\n-- \nCheers,\n\nSverre Rabbelier\n"}]}