public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Marek Zawirski <marek.zawirski@gmail•com>
To: "Jean-François Veillette" <jean_francois_veillette@yahoo•ca>
Cc: git@vger•kernel.org, Robin Rosenberg <robin.rosenberg@dewire•com>,
	"Shawn O. Pearce" <spearce@spearce•org>
Subject: Re: [EGIT] Supported Eclipse version
Date: Fri, 25 Jul 2008 16:12:25 +0200	[thread overview]
Message-ID: <4889DF49.3000903@gmail.com> (raw)
In-Reply-To: <89D1384A-403C-4E6E-816C-204AE0AAC30C@yahoo.ca>

Jean-François Veillette wrote:
>> Maybe some users (or developers) from mailing list can tell us about 
>> their opinion?
>
> I think keeping comptability for one version behind the 'current' 
> (still compatible 3.3 while 3.4 is the current) is a reasonable goal.
> 3.2 is relatively far behind, tools vendor had time to get up to date 
> by now.
> If a user is using a third party version of eclipse based on 3.2, then 
> I guess he should not expect egit to work with it (he should just pray 
> and hope for the best).
>
> For myself, I use 3.3.x, I have not yet moved to 3.4 since my main 
> plugin (WOLips) is not ready yet for 3.4.
>
> - jfv
I would also vote for this change. Especially if there are not many 
users screaming that they need egit in Eclipse 3.2.

BTW, I'm using 3.4 version for 2 days and it looks really nice. What's 
important, it seems to not be that buggy as early 3.3 releases were.

Robin, Shawn, would you accept next patches using 3.3 API?

Marek

  reply	other threads:[~2008-07-25 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 13:57 [EGIT] Supported Eclipse version Marek Zawirski
2008-07-24 14:07 ` Jean-François Veillette
2008-07-25 14:12   ` Marek Zawirski [this message]
2008-07-25 16:16     ` Shawn O. Pearce
2008-07-25 19:35       ` 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=4889DF49.3000903@gmail.com \
    --to=marek.zawirski@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jean_francois_veillette@yahoo$(echo .)ca \
    --cc=robin.rosenberg@dewire$(echo .)com \
    --cc=spearce@spearce$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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