From: Noel Grandin <noel@peralex.com>
To: Imran M Yousuf <imyousuf@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Carlos Rica <jasampler@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: GSoC 2008 - Mentors Wanted!
Date: Wed, 05 Mar 2008 16:55:11 +0200 [thread overview]
Message-ID: <47CEB44F.9040404@peralex.com> (raw)
In-Reply-To: <7bfdc29a0803050025p45dfcea9q87a1107a8bed46a6@mail.gmail.com>
Imran M Yousuf wrote:
> To start with I was actually thinking of JNI + "exec from C". So later
> when libification is completed we can replace the execs with call to
> the libs directly instead. Is this a viable fourth option (sorry I
> forgot to mention it the first time around)?
>
>
This is probably a good idea. JGIT is always going to be 2 steps behind
the native GIT code when comes to accessing on-disk structures.
This is also how the subversion plugin for the Eclipse IDE worked in the
beginning and the performance seemed to be acceptable (to me).
Regards, Noel.
Disclaimer: http://www.peralex.com/disclaimer.html
next prev parent reply other threads:[~2008-03-05 15:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 5:11 GSoC 2008 - Mentors Wanted! Shawn O. Pearce
2008-03-04 9:23 ` Matthieu Moy
2008-03-05 6:06 ` Shawn O. Pearce
2008-03-04 17:14 ` Jakub Narebski
2008-03-04 20:47 ` Carlos Rica
2008-03-04 20:51 ` Carlos Rica
2008-03-05 5:36 ` Shawn O. Pearce
2008-03-05 7:58 ` Imran M Yousuf
2008-03-05 8:15 ` Shawn O. Pearce
2008-03-05 8:25 ` Imran M Yousuf
2008-03-05 8:33 ` Imran M Yousuf
2008-03-05 14:55 ` Noel Grandin [this message]
2008-03-05 16:37 ` Johannes Schindelin
2008-03-06 4:58 ` Shawn O. Pearce
2008-03-05 21:13 ` Robin Rosenberg
2008-03-06 5:08 ` Shawn O. Pearce
2008-03-06 5:19 ` Imran M Yousuf
2008-03-06 11:04 ` Johannes Schindelin
2008-03-06 20:48 ` Robin Rosenberg
2008-03-06 5:33 ` Imran M Yousuf
2008-03-06 20:47 ` Robin Rosenberg
2008-03-06 5:06 ` Christian Couder
2008-03-06 5:31 ` Christian Couder
2008-03-06 6:44 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47CEB44F.9040404@peralex.com \
--to=noel@peralex.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=imyousuf@gmail.com \
--cc=jasampler@gmail.com \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.