4 ms·
Its part of a bigger issue - source control tools have wildly different fundamental models. Moving to git from anything else will be confusing, because users ju
by JoeAltmaier 7y ago
Its part of a bigger issue - source control tools have wildly different fundamental models. Moving to git from anything else will be confusing, because users jump to conclusion about what commands and operations are doing. Its different from other tools in important ways.
- huherto 7y agoI moved from SCCS to RCS to CVS to Subversion to Git. Moving to Git was the more difficult step for me. I prefer it now. For a while I had to move back to Subversion and I hated it.
- touisteur 7y agoCan't use svn for the life of me, though I used it for 10 years before trying git for a real dvcs need (remote team for a while)... Just the idea pains me. Missing git add -p, cherry-pick & rebase -i so much I immediately put git-svn on if I have to go back... Also, it makes telecommuting easier, asynchronous team work so much simpler... I think the key 'abstraction' that people don't understand is cherry-pick. I can't explain clearly in fine details /how/ it works, but it is the base of so much of git's power...