Sverre Rabbelier <srabbelier@xxxxxxxxx> writes: > ;). 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. Isn't fast-import designed to be used as a downstream side of a pipe that is fed by an independent program you write (and may link with libsvn)? It wouldn't care what license that data producer program is distributed under. On the fast-export side the issue should ideally be the same. Your new program that may link with libsvn reads from the datastream that comes from the git repository via pipe as an independent process to propagate the changes to the subversion side. You may need to have/keep additional info on commits for roundtrip, but that is between the part of your program that feeds fast-import and the other part of your program that consumes the output from fast-export. fast-import may need to be told to export mark, and you pick them up to see what commits resulted on the git side from what you fed it, and later use that information when reading from fast-export to propagate new things back to subversion side. No? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html