Hi Ram, On Mon, 22 Mar 2010, Ramkumar Ramachandra wrote: > > Don't know about importer modes, but in native connection mode it is > > possible to avoid calling or linking to git in any way (been there, > > done that). > > > 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. > > As of this point, I'm undecided about which parts of Git Core to link > to, if at all. I'll try to avoid linking, but I'll do whatever is most > convenient within the bounds of the license as I write the remote > helper. AFAICT the git-remote idea is to use a text protocol (which may lend itself to be copied by Mercurial at some stage, a clear sign that we did something well when that happens). > > Because it's much better for everyone at the end of the GSoC if only > > half of the project is finished but merged, rather than if all the > > project is "finished" but nothing can be merged. > > Right. I'll merge the whole thing in 3-4 phases then. I am sure that Sverre will be of tremendous help to decide when is the opportune moment to show off your code. Ciao, Dscho -- 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