From: Robin Rosenberg <robin.rosenberg@dewire.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, 5 Mar 2008 22:13:20 +0100 [thread overview]
Message-ID: <200803052213.20501.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <7bfdc29a0803042358n6126286dr7a17f3b4dadbabe5@mail.gmail.com>
Den Wednesday 05 March 2008 08.58.15 skrev Imran M Yousuf:
> I would like to suggest 2 projects that I want to work as a developer
> (and/or mentor):
>
> 1. GIT SCM Plugin for NetBeans (GPLv2 with CPE, same as NetBeans)
> The aim of the plugin is to integrate GIT with NetBeans using JNI so
> that any change in the implementation of GIT does not effect the SCM
> plugins way of work.
> Language: Java
> Goal: Make GIT available from IDE for NetBeans users and use GIT using
> Java Native Interfaces
As the current acting maintainer or egit/jgit I would not mind cooperating
with making it available to Netbeans, J2EE and command line interface or
whatever.
You can make a plugin for Netbeans today that will do the basic like walking
the history, finding out what to commit, commit, switch/create/reset
branches, decorations based on jgit and you wouldn't need to change a thing
in jgit. There might be things you *want* to change, but that's another story
and applied to the continued development for the Eclipse plugin too. Even
the license might be changed.
You will find support in jgit for this today. Cloning over git and ssh real
soon. I'm clensing the oopses from the history right now. (bless rebase -i
and git-gui).
There are no dependencies on Eclipse and I do not plan on introducing any.
Jgit and Egit live in the same repo at the moment simply because there are
no other users of egit so far.
There might be some operations that might be harder to do well in Java. For
those exec'ing might be the solution, I'm thinking repack, but then I haven't
tried it yet. In general jgit is almost as fast as git and probably
outperforms git on windows as git there doesn't use memory mapped I/O for
packs (something I'd expect someone or even me to fix soon). For JNI'ed
operations the complexity is just horrible and even when possible, there is
a lot of overhead for JNI itselt, conversion from UTF-16 to somehing
eightbitish and back. On windows there's even yet another layer of
eight-bitish to UTF-16 and back in the Win32 API. Jgit also uses memory
mapped I/O on all platforms that support it for pack reading.
If someone *did* make a fully reentrant libgit, I'd be inclined to balance my
opinions differently.
-- robin
next prev parent reply other threads:[~2008-03-05 21:15 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
2008-03-05 16:37 ` Johannes Schindelin
2008-03-06 4:58 ` Shawn O. Pearce
2008-03-05 21:13 ` Robin Rosenberg [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200803052213.20501.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).