GIT (was: Coverity Scan)
Fri Apr 25 23:35:00 GMT 2014
Greetings, Jim Garrison!
>> -----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.
This is exactly what makes me dislike it strongly. This, and idiotic model of
copying whole repository to my machine, when I only want to glance at the
source code, and find the culprit of my current issues.
I've spent 3 hours downloading a 200Mb repo of a project, where the Subversion
client pulled 4 or 5Mb HEAD of it in like 10 minutes, once I realized what an
idiotic weight I pulled and went to google to see if it can be done better.
And "fine control" doesn't mix with "project consistency" at all.
Subversion is aimed at versioning of a whole project, in a supposedly
consistent state at each version. What can be more "fine" than this, is beyond
You can still commit separate files from working copy, though, but this
practice is discouraged for the greater good of the project you develop.
> 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
Andrey Repin (email@example.com) 26.04.2014, <03:19>
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin