- not very intuitive from the SVN camp, you need more than an hour to get everything set up.
- need to learn new ways to do old subversion jobs, not straight forward,
- upon frustration of pulling with conflict, reset and rebase will erase your work, and it is gone forever, you have to redo the code.
- even after you replace with head revision for the files, they still shows up in the unstaged changes.
- generate and reuse header if too complicated.
- I am sure I can spend a day to concentrate on it , I will get everything right, but I did not spend more than one hour in SVN, and I had never have to redo the coding.
- I sense half of the team think it is unnecessarily complicated.
Tuesday, April 08, 2014
git, I hate it now
I am in a small size team(10), we switched from SVN to git+gerrit , after a while I really hate to use this setup.
Subscribe to:
Post Comments (Atom)
1 comment:
git's original intent was not for every project's source code management needs - it was built solely for the purpose of managing Linux's kernel source code.
I am rather amazed so many people have bought into it as a "one size fits all" solution.
Then again, I was rather surprised when people thought RDBMSs were suitable for every need.... and look where we are now (finally getting away from their use for everything).
Ciao
Post a Comment