From: "Shawn O. Pearce" <spearce@spearce•org>
To: Marek Zawirski <marek.zawirski@gmail•com>
Cc: Jean-Frannnois Veillette <jean_francois_veillette@yahoo•ca>,
git@vger•kernel.org, Robin Rosenberg <robin.rosenberg@dewire•com>
Subject: Re: [EGIT] Supported Eclipse version
Date: Fri, 25 Jul 2008 11:16:52 -0500 [thread overview]
Message-ID: <20080725161652.GA21117@spearce.org> (raw)
In-Reply-To: <4889DF49.3000903@gmail.com>
Marek Zawirski <marek.zawirski@gmail•com> wrote:
> 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.
>
> Robin, Shawn, would you accept next patches using 3.3 API?
Yes, we should be dropping support for 3.2 now and supporting only
3.3 and 3.4 going forward. 3.2 is ancient and anyone who is serious
aboug using Git with Eclipse really should be on a more current
version of the tools.
Same argument that Junio gave about not supporting Debian users who
are still installing git 1.4.4.4 and hope it works; we suggest they
install the 1.5.x based backport as soon as possible.
Commercial Eclipse distributions that are still based upon 3.2
should be upgrading themselves to 3.3 real soon, and if not, their
users should be forching them to do it.
--
Shawn.
next prev parent reply other threads:[~2008-07-25 16:17 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
2008-07-25 16:16 ` Shawn O. Pearce [this message]
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=20080725161652.GA21117@spearce.org \
--to=spearce@spearce$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=jean_francois_veillette@yahoo$(echo .)ca \
--cc=marek.zawirski@gmail$(echo .)com \
--cc=robin.rosenberg@dewire$(echo .)com \
/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