Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] Google Summer of Code 2010 project proposal for EGit/JGit projects

On Sat, Mar 20, 2010 at 8:46 AM, Dariusz Luksza
<dariusz.luksza@xxxxxxxxx> wrote:
> Most of developers doesn't use full power (or maybe even 80-70%) Eclipse,
> so theoretically it would be easy to fulfill they requirements.

I am not sure this is the right way to look at it, to be honest.

> Right now I'm use "Team Synchronization perspective" only to commit and
> retrieve changes from CVS, rarely I use it for resolving conflicts and
> "blaming".

My point is that you can do all of this in the Java perspective and
many developers (me included) prefer that approach as it means less
context switches for things that are done often. There was a
discussion in #eclipse-dev (IRC channel) at some point and many used a
small number of perspectives (often just Java and Debug). To make it
clear, these are experienced Eclipse users

> During GSoC (if we can get a slot) I'll try to integrate
> witch TSP (Team Synchronization perspective) so that regular CVS user
> doesn't see a difference between CVS and Git.

Git is different from CVS, I believe that emulating CVS blindly is not
the best approach. In Git, you have the staging area, commits are
local, you have the concept of push/pull, local/remote branches, etc.
I don't know what others think, but my suggestion is for you to _also_
check what Git-specific UI tools do and take that into account.

Best,
Ismael


Back to the top