This is the mail archive of the
mailing list for the Cygwin project.
GIT (was: Coverity Scan)
- From: Jim Garrison <jim dot garrison at nwea dot org>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Fri, 25 Apr 2014 15:24:17 +0000
- Subject: GIT (was: Coverity Scan)
- Authentication-results: sourceware.org; auth=none
> -----Original Message-----
> Corinna Vinschen
> Sent: Friday, April 25, 2014 6:33 AM
> > >> There have been a few hints on this list about a possible move
> > >> from CVS to git. If such a move were on the cards then that should
> > >> probably happen first - I wouldn't want the nugatory effort of
> > >> getting this working from CVS only to have to change it almost
> > >Yeah, I'm n ot exactly looking forward to it since I'm very familiar
> > >with CVS or SVN, but have nothing but trouble with git. But since
> > >everybody else is so very happy with git, I guess I'll have to adapt.
> > >Teeth-gnashingly.
I recently went through the same reluctant switch to Git from SVN.
I can tell you from personal experience that there's a period of disorientation when even the simplest tasks require a quick trip to Google. And Git requires a major shift in your mental model of how things work. Instead of 2 places where stuff is (local and remote) there are now 4 (workspace, stage, local repo, remote repo).
HOWEVER... once you get over the learning hump you see that Git is MUCH better and allows much finer control over what's happening. Plus, the online documentation is very good, and questions have been asked enough times that Google serves up good answers to just about any question. If you have Cygwin/X installed, the "git gui" and "gitk" tools will make the transition easier.
I started learning Git in earnest back in December, and really started "thinking in Git" soon after. Now, if I had to go back I would be disappointed.