From: Jakub Narebski <jnareb@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Subject: Re: [RFC (take 2) Git User's Survey 2007
Date: Tue, 31 Jul 2007 02:45:55 +0200 [thread overview]
Message-ID: <200707310245.56077.jnareb@gmail.com> (raw)
In-Reply-To: <20070731003251.GW20052@spearce.org>
Shawn O. Pearce wrote:
> Jakub Narebski <jnareb@gmail.com> wrote:
> > How you use GIT
> >
> > 8. Which porcelains do you use?
> > (zero or more: multiple choice)
> > - core-git, cogito, StGIT, pg, guilt, egit (Eclipse), other
> > 9. Which git GUI do you use
> > (zero or more: multiple choice)
> > - gitk, git-gui, qgit, gitview, giggle, tig, instaweb,
> > (h)gct, qct, KGit, other
>
> I'll give you git-gui as a GUI here instead of a porcelain.
>
> But I *seriously* object to calling egit a porcelain. egit is a
> complete reimplementation of git in Java. Calling it a porcelain
> is wrong. Robin, David and myself have put a considerable amount
> of effort into keeping egit 100% pure Java, so it is Write Once,
> Test Everywhere.
>
> The _only_ code that egit has borrowed from core Git has been the
> packfile delta decompressor. Everything else is a reimplementation.
> Just not 100% blackbox, as the egit developers have looked at the
> core Git source before. Heck, we have even been known to contribute
> a patch here or there to core Git. :)
>
> All of the other porcelains that you listed reuse the core Git
> plumbing and are thus true porcelain. But egit doesn't.
O.K. I was not sure where to put egit (if put it at all).
Implementations? Currently we have core-git in C, egit in Java (what is
the progress report on this front?), and there was GSoC project of
Git.NET (but it didn't start I think).
Do you want question about egit in the survey?
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-07-31 0:46 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 1:58 Git User's Survey 2007 Jakub Narebski
2007-07-25 16:19 ` Marco Costalba
2007-07-26 4:52 ` Steven Grimm
2007-07-27 11:20 ` [RFC] " Jakub Narebski
2007-07-27 12:21 ` Nguyen Thai Ngoc Duy
2007-07-27 13:01 ` Andy Parkins
2007-07-27 19:07 ` Jakub Narebski
2007-07-28 8:02 ` Andy Parkins
2007-07-29 16:50 ` Paolo Ciarrocchi
2007-07-29 17:05 ` Paolo Ciarrocchi
2007-07-30 0:21 ` Jakub Narebski
2007-07-30 3:35 ` Shawn O. Pearce
2007-07-30 13:40 ` Jakub Narebski
2007-07-30 7:44 ` Paolo Ciarrocchi
2007-07-30 13:26 ` Jakub Narebski
2007-07-30 19:26 ` David Kastrup
2007-07-30 21:12 ` Junio C Hamano
2007-07-30 21:37 ` Jakub Narebski
2007-07-30 22:38 ` David Kastrup
2007-07-30 21:25 ` Nguyen Thai Ngoc Duy
2007-07-30 21:35 ` Jakub Narebski
2007-07-30 20:56 ` [RFC (take 2) " Jakub Narebski
2007-07-31 0:32 ` Shawn O. Pearce
2007-07-31 0:45 ` Jakub Narebski [this message]
2007-07-31 1:09 ` Shawn O. Pearce
2007-07-31 1:24 ` Junio C Hamano
2007-07-31 1:31 ` Shawn O. Pearce
2007-07-31 11:22 ` Jakub Narebski
2007-07-31 11:33 ` Paolo Ciarrocchi
2007-07-31 12:30 ` Jakub Narebski
2007-07-31 16:35 ` Git User's Survey 2007 - web survey site Jakub Narebski
2007-07-31 19:07 ` Paolo Ciarrocchi
2007-08-02 4:51 ` Martin Langhoff
2007-08-02 13:04 ` Paolo Ciarrocchi
2007-08-04 0:50 ` [RFC (take 3)] Git User's Survey 2007 Jakub Narebski
2007-08-04 5:41 ` Shawn O. Pearce
2007-08-04 12:10 ` Jakub Narebski
2007-08-04 7:40 ` David Kastrup
2007-08-05 20:06 ` Jakub Narebski
2007-08-06 0:29 ` Johannes Schindelin
2007-08-05 9:30 ` Asger Ottar Alstrup
2007-08-06 1:17 ` Jakub Narebski
2007-08-06 5:48 ` Asger Ottar Alstrup
2007-08-06 15:44 ` Jakub Narebski
2007-08-05 20:51 ` [RFC (take 4)] " Jakub Narebski
2007-08-14 1:51 ` [RFC (final)] " Jakub Narebski
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=200707310245.56077.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=paolo.ciarrocchi@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 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 NNTP newsgroup(s).