Re: JGit vs. Git

From: Stephen Bannasch <stephen.bannasch@deanbrook.org>
Date: Jan 6, 2009, 19:55 UTC
Message-ID: <p06240805c589657fd75a@[192.168.1.114]>
In-Reply-To: <200901061212.07240.robin.rosenberg.lists@dewire.com>

At 12:12 PM +0100 1/6/09, Robin Rosenberg wrote:

Show 10 quoted lines

>tisdag 06 januari 2009 07:50:11 skrev Vagmi Mudumbai:
>  > I am working on Windows with msysGit behind a HTTP Proxy. (Life cant
>>  get worse, I guess.) . I planned on using grit via JRuby but grit uses
>>  fork which is not available on funny platforms like windows. And JRuby
>>  guys do not have any plan on supporting fork even on platforms on
>>  which for is supported. If JGit is a pure Java based implementation of
>fork isn't really supported on Windows. Cygwin goes to great lengths to
>emulate it. Trying to do that within the context of an arbitrary JVM seems
>like a daunting task. Consider submitting patches to make grit not use fork...
>just kidding.., please help us improve JGit instead :)

Or think about extending the Ruby gem grit to also use JGit. Which would certainly improve grit and probably help improve JGit also.

I've thought about this a bit -- but it hasn't gotten to the top of my list yet ...

There are some examples of Ruby Gems which use Java libraries when run in JRuby and native C libraries when used from MRI.

   hpricot:   http://github.com/why/hpricot/tree
   redcloth:  http://github.com/jgarber/redcloth/tree/master