[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
We can tell the EGit folks to start a feature parity wiki
page ;-)
I haven't tried it yet, but James more or less summarizes my feelings. Wait
till there is near parity.
===========================
Chris
Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
James
Blackburn ---06/03/2010 12:29:03 PM---I use git day to day here to track CDT
CVS, it works remarkably well, and git's margic merging is a
From: |
James Blackburn
<jamesblackburn@xxxxxxxxx> |
To: |
"CDT General developers list."
<cdt-dev@xxxxxxxxxxx> |
Date: |
06/03/2010 12:29 PM |
Subject: |
Re: [cdt-dev] Git plans? |
Sent by: |
cdt-dev-bounces@xxxxxxxxxxx |
I use git day to day here to track CDT CVS, it works
remarkably well,
and git's margic merging is a real time saver!
That
said I'd be against moving to egit until all the day-to-day
workflows can
be easily and safely accomplished in the IDE.
To be forced to the command
line for merge (for example) would
introduce a barrier to entry not present
for CVS users. Especially
for those sat on Windows where native git
has traditionally been weak.
0.9 may have everything we need andI'm all for
being a bleeding edge
user, but I'd rather we started from a point where
the tooling has
feature parity with
CVS.
Cheers,
James
On 3 June 2010 16:36, Alex Blewitt
<alex.blewitt@xxxxxxxxx> wrote:
> Now that Helios is out of the
door, what are the thoughts with regards to
> migrating to
Git?
>
> The EGit plugin was released recently, and whilst it
shows promise in a
> number of ways, general case merging is still
lacking. There is a plan to
> have that in September or so with EGit
0.9.x that should have that
> functionality.
>
> It can be
used in conjunction with the command line git tools though.
> However,
merge conflicts may not be handled properly in the EGit plugin,
> which
is probably one of the more important use cases.
>
>
Alex
>
> Sent from my (new) iPhone
>
_______________________________________________
> cdt-dev mailing
list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
_______________________________________________
cdt-dev
mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
