From: Shawn Pearce <spearce@spearce.org>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: git@vger.kernel.org
Subject: Re: egit/jgit wishlist
Date: Mon, 4 Dec 2006 13:29:02 -0500 [thread overview]
Message-ID: <20061204182902.GG6011@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0612041841280.14187@alpha.polcom.net>
Grzegorz Kulewski <kangur@polcom.net> wrote:
> I think that doing it in 100% pure Java is ok in long run but I wonder if
> you couldn't make "wrapper" plugin for a start (that would call the real C
> git for every operation) and make it usable (with full pure Java SWT UI
> support) and then try to implement feature by feature in pure Java (with
> config options telling what should be called by wrapper and what by pure
> implementation)?
Several people have proposed doing exactly that, but thus far
myself and Robin Rosenburg have been the only two to step forward
with code. I personally want to avoid calling external programs
as much as possible here, and that means staying with a 100% pure
Java implementation. Hence the desire to not build a wrapper plugin.
We have the core repository reading and writing working. We can
write out trees. We can create commits (we just lack UI for it).
So we're part of the way there...
--
next prev parent reply other threads:[~2006-12-04 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 17:28 egit/jgit wishlist Shawn Pearce
2006-12-04 17:58 ` Steven Grimm
2006-12-04 18:05 ` Shawn Pearce
2006-12-04 18:16 ` Grzegorz Kulewski
2006-12-04 18:29 ` Shawn Pearce [this message]
2006-12-04 21:19 ` Steven Grimm
2006-12-04 21:47 ` Grzegorz Kulewski
2006-12-04 22:06 ` Steven Grimm
2006-12-05 8:37 ` Johannes Schindelin
2006-12-04 21:54 ` Robin Rosenberg
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=20061204182902.GG6011@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=kangur@polcom.net \
/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.