From: Noel Grandin <noel@peralex.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Any news on an Eclipse plugin?
Date: Tue, 07 Mar 2006 08:59:26 +0200 [thread overview]
Message-ID: <440D2F4E.9090009@peralex.com> (raw)
In-Reply-To: <20060306173229.GA27965@spearce.org>
[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]
The subversion plugin (subclipse.tigris.org) might be a good starting
point since it delegates a lot of it's low-level work through an
interface called svnClientAdapter. Re-implementing that to talk to git
should get you something useful in a reasonable time-frame.
Note that an eclipse team plugin is a pretty complicated beast.
Shawn Pearce wrote:
>I'm considering starting an Eclipse plugin for GIT. So I did
>some digging to see if any existing projects have anything I can
>contribute to (rather than starting from scratch) but I only turned
>up a thread from May 2005 started by Jon Seymour:
>
> http://www.gelato.unsw.edu.au/archives/git/0505/3357.html
>
>anyone know anything newer? If there's nothing existing worth
>starting with other than the CVS or SVN plugins (as mentioned in
>this thread) I'll probably start putting together a prototype and
>start making it available early next week.
>
>I'm going to carefully read the thread that I linked to above before
>writing anything, so there's no need to start getting into the core
>and not so core discussion again. I'll read it over for myself. :-)
>
>
>
NOTICE: Please note that this email, and the contents thereof,
are subject to the standard Peralex email disclaimer, which may
be found at: http://www.peralex.com/disclaimer.html
If you cannot access the disclaimer through the URL attached
and you wish to receive a copy thereof please send
an email to email@peralex.com
next prev parent reply other threads:[~2006-03-07 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 17:32 Any news on an Eclipse plugin? Shawn Pearce
2006-03-07 6:59 ` Noel Grandin [this message]
2006-03-12 19:50 ` lamikr
2006-03-13 4:09 ` Shawn 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=440D2F4E.9090009@peralex.com \
--to=noel@peralex.com \
--cc=git@vger.kernel.org \
--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.