Re: [cdt-dev] Why CDT should switch to Git

[James Blackburn <jamesblackburn@xxxxxxxxx>]

On 22 December 2010 08:31, Alex Blewitt <alex.blewitt@xxxxxxxxx> wrote:
> I think this blog entry, on how SpringSource uses git, hits the nail on the head on what Git enables.
>
> http://blog.springsource.com/2010/12/21/social-coding-in-spring-projects/

I wholeheartedly agree!

Unfortunately, it's a shame that "Compare with..." is marked as an
enhancement -- I think it's the major missing piece in the usability
puzzle.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=327077
https://bugs.eclipse.org/bugs/show_bug.cgi?id=327088

It's non-intuitive to preview changes, by clicking on the commit
action (where you can no longer edit source...).

Also the Synchronize dialog is confusing, and doesn't scale to large
repositories.  Try attempting to compare changes in o.e.core.resources
with a local branch - the refs drop-down lists every date tag
(vYYYYMMDD):
https://bugs.eclipse.org/bugs/show_bug.cgi?id=333065
so you can't get to the branch you want.  If you type the name, you get a AIOOB:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=333063
I discovered that you can use the page up to get to the top of the
list, then the down arrow to iterate through. But it's really not
intuitive.

I also miss line annotation in the UI.  When chasing bugs, I always
want to know what bugzilla / commit lead to a particular line being as
it is.

It's great how many of git's features jgit and egit now support.
However without supporting the basic pull, compare, push workflow -
how can we recommend this as a CVS alternative?  For *nix users, ok we
can drop down the command line, but is this feasible for developers on
windows?

Cheers,
James