From: A Large Angry SCM <gitzilla@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
James Linder <james.h.linder@gmail.com>,
git@vger.kernel.org
Subject: Re: NYU Open Source Programming Class Releases JavaGit API 0.1.0 Alpha
Date: Mon, 04 Aug 2008 20:03:58 -0400 [thread overview]
Message-ID: <489798EE.7050402@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0808050127510.9611@pacific.mpi-cbg.de.mpi-cbg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Mon, 4 Aug 2008, Shawn O. Pearce wrote:
>
>> James Linder <james.h.linder@gmail.com> wrote:
>>
>>> Jgit/Egit, on the other hand, appear to be tightly integrated with
>>> Jgit primarily supporting Egit.
>> That's not really true.
>
> I started using jgit in a project that is not yet totally public. It is
> awesome. (I mean jgit is awesome, even if my project does make me happy,
> too.)
>
> And I absolutely share the puzzlement of Shawn why anybody would try to do
> their own thing in Java, instead of contributing to jgit.
>
> Especially the fact that "JavaGit" seems to repeat the all-to-obvious
> error of Eclipse: to make a platform-independent library that depends on
> platform dependent components.
>
> I find that kind of thinking so strange, to the point that I am really
> amazed enough to want to analyze the brain of the people inventing such
> things.
>
> But hey, maybe there is a deeper point in it that escapes me.
You mean like "Why is a project with the goal of bringing the power of
git to Java developers hosted in svn instead of git"?
next prev parent reply other threads:[~2008-08-05 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 16:48 NYU Open Source Programming Class Releases JavaGit API 0.1.0 Alpha James Linder
2008-08-04 17:54 ` Shawn O. Pearce
2008-08-04 23:36 ` Johannes Schindelin
2008-08-05 0:03 ` A Large Angry SCM [this message]
2008-08-05 1:10 ` Petr Baudis
2008-08-05 1:20 ` Shawn O. Pearce
2008-08-05 1:32 ` Pieter de Bie
2008-08-05 1:46 ` 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=489798EE.7050402@gmail.com \
--to=gitzilla@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=james.h.linder@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).