This is the mail archive of the
mailing list for the Cygwin project.
Re: GIT (was: Coverity Scan)
- From: Reini Urban <rurban at x-ray dot at>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Fri, 25 Apr 2014 15:42:38 -0500
- Subject: Re: GIT (was: Coverity Scan)
- Authentication-results: sourceware.org; auth=none
- References: <0C723FEB5B4E5642B25B451BA57E2730751B9B9A at S1P5DAG3C dot EXCHPROD dot USA dot NET> <20140425162224 dot GL5666 at calimero dot vinschen dot de>
On Fri, Apr 25, 2014 at 11:22 AM, Corinna Vinschen wrote:
> On Apr 25 15:24, Jim Garrison wrote:
>> > Corinna Vinschen
>> > > >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).
> Yeah, I'm trying to get a grip via "the book" http://git-scm.com/book/
Only experience helps.
I needed about a year to not loose too much changes after the switch
from svn to git, but feeling very happy now.
It helps having backups for the beginning if you try out rebase or
reset --hard or
git pull --force.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple