On Sun, 21 Mar 2010, Ramkumar Ramachandra wrote: > Hi, > > > The structure for remote helpers should be that each foreign system has a > > single helper which git can call with instructions on what to do (both for > > foreign-to-git and for git-to-foreign operations). So 3 and 4 have to be > > functions of the same program, and it's probably best for 2 and 5 and > > maybe 1 to also be part of this program. > > I've attached a small image specifying the relationship between > various components. I plan to include a more elaborate version of this > in my final proposal. Is this what you had in mind? Mostly, except that I think it should be possible to avoid having git-remote-svn actually link to the git core, because the git core should be taking care of everything git-specific for you. Of course, the git core also provides a bunch of useful C library code that you may want to use, such as a nice string buffer implementation, so you may want to link to git even if you don't actually need it, if licenses are suitable and it would be convenient. -Daniel *This .sig left intentionally blank* -- 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