SVN [LWN.net]

SVN

Posted Feb 5, 2008 19:09 UTC (Tue) by bronson (subscriber, #4806)
In reply to: SVN by ceplm
Parent article: Linux Gazette #147

There actually is a git-on-Eclipse plugin.  It's basically git functionality 100%
re-implemented in Java.  Don't bother with it, though: it has a few issues and is now quite
out of date.

The much better way to handle this, of course, would be to slice a libgit out of git's
codebase.  Eclipse, Anjuta, etc would link against libgit and a single codebase would handle
everything.  No muss, no fuss.

Unfortunately, git was quite consciously written to just abandon memory when when it's done.
Just terminating and letting the OS clean everything up is *much* faster than meticulously
paging in and freeing every little data structure.

Problem is, run this code in a persistent app and what happens?  Memory leak city.  Scary in
scale.

So, the Git team are working on cleaning up the leaks and arranging a libgit.  It's a huge
undertaking though and, last I heard though (6 months ago?) it's still a long way off.  Sigh.

bzr's Eclipse bindings are pretty darned great BTW.  They're definitely worth a look if you
want to do distributed-on-Eclipse.

to post comments

SVN

Posted Feb 6, 2008 9:58 UTC (Wed) by ceplm (subscriber, #41334) [Link] (1 responses)

Yeah, libgit would be awesome. I was using RCS for a lot of time, and so I have plenty of RCS
repositories -- it would be actually better to convert these directory to .git repositories
instead of getting through CVS. There is git://people.freedesktop.org/~keithp/parsecvs for
that, but it requires libgit. Oh well.

SVN

Posted Feb 6, 2008 23:52 UTC (Wed) by nix (subscriber, #2304) [Link]

I see no reason why a programmatic interface to git's tools that forks 
them off and talks to them via pipes couldn't be written. It wouldn't even 
be hard. (I'm not sure it's worth it, though: it's not as if it's 
difficult for people who need to talk to git via pipes to do so now.)